This page is the concise source-scope snapshot for resuming work. It distinguishes implemented surfaces from live acceptance and links to the contracts that carry the details. Last source review: 2026-08-26.
The 2026-08-18 verification baseline is dated history for its named tree and commands. It is not an eternal test count, a promise that provider auth is still healthy, or proof of an untested external environment. Check the current tree and verification ledger before repeating a claim.
| Surface | Implemented scope | Evidence boundary and canonical detail |
|---|---|---|
| Metrics Dashboard | Exactly four stable identities × Claude/Codex = eight fixed lane rows, exact-account Capacity/Activity, read-only projection of the Orchestrator-owned signed snapshot for Codex, owner-selected provider rows, Azure/custom cards, responsive layout, filters, trends, and authenticated Dashboard bridge | Connection and lane identity/readiness never prove an independent reading's intent, authority, availability, or freshness. Provider-free regressions prove fixtures/local behavior; exact live readings require current identity/route checks. The container has no Codex runtime or credential authority. See server/README.md. |
| Cacheboard Orchestrator | Fixed-lane exact-session inventory/control, multi-session admission and encrypted local queueing, Codex saved-credential refresh/exact-email metrics collection and signed snapshot publication, adoption safeguards, Attention, audit, backup/restore, capability catalog, and a local-first controller hierarchy with route-scoped resource loading | Windows Orchestrator is the sole active Codex credential writer. A provider-free authenticated browser fixture covers desktop and narrow first-view layout, local/advanced request isolation, stale advanced-failure isolation, host-status-before-setup ordering, keyboard disclosure activation, measured targets, narrow containment, reduced-motion emulation, and Tasks-only Sortable loading. It does not prove live provider effects, a configured remote host, a real mobile device, or assistive-technology behavior. See the Orchestrator map. |
| Cacheboard Tasks | Desktop-first six-state Kanban workspace plus private human-owned Quick Notes, with bounded per-column scrolling, workflow jumps, global/inline capture, actionable Focus, search/filters, progressive project editing, a one-project master/detail cockpit, guarded unsaved detail edits, responsive movement, reversible lifecycle, title-only Quick Note task starters, and a read-only execution-admission preview | Current Orchestrator schema 11 contains unchanged schema-10 Work Items plus separate local-plaintext Quick Notes. The Project cockpit summarizes only already-loaded, exact-related current-browser Tasks/Focus and read-only Sessions/Rooms/Automations; unknown is Not loaded, retained prior evidence stays visibly stale, and it grants no runtime or repository authority. Task starters create only owner-reviewed ordinary Inbox drafts; execution readiness is current browser evidence and grants no admission or authority. Work Items/Quick Notes and authenticated browser regressions are provider-free evidence only unless the exact current tree is recorded otherwise; they make no live-provider or real-device claim. See work-items.md and ADR 0007. |
| Cacheboard Productivity | Desktop-first daily workbench at /productivity: server-derived Focus queue, selected-task focus/break countdown with one current-document 15/25/50-minute preferred work preset, current-document session pulse, bounded multi-task Brain Dump, and deterministic Get unstuck guidance |
Productivity adds no backend, schema, scheduler, provider call, or durable time record. Timer/session observations, preferred work preset, and unsent draft/retry state are document-memory only; proven Brain Dump creates persist as ordinary canonical Inbox Work Items. Source presence is not live acceptance. See productivity.md and the pinned provenance record. |
| Project Rooms and automations | Isolated branches/worktrees, path leases, writer claims, explicit context delivery, deterministic DAG recipes, human gates, restart recovery, and held execution admission | Fixture coverage and dated local/live receipts vary by operation. Recheck the Room contract and automation contract. |
| Existing and remote chats | Bounded local discovery/observation/safe adoption plus packaged outbound Windows/Linux/macOS host agents for exact-profile read-only remote lifecycle control | Local/adoption and host-fabric fixtures do not prove a currently enrolled remote machine. See universal control plane. |
| Private mobile controller | Responsive controller and single-use, exact-origin private-tailnet pairing flow; execution remains on an enrolled computer | Browser/pairing fixtures do not prove an iPhone or live tailnet. See tailnet mobile gateway. |
| Typed connectors | Pinned SSH observation, cloud target descriptors, immutable container/pod observation requests, and typed wmux-owned terminal control | Packaged/fixture support is distinct from a configured live target. See connector service. |
| Tools, Memory, and Codex Cloud | Exact-chat local skill/plugin activation, curated context_only memory, and version-pinned experimental Codex Cloud list/status/diff support |
Remote asset activation is unavailable; Codex Cloud submission is disabled by default and separately gated. See provider capability matrix. |
The shared rail now has three top-level areas: expandable AI, Tasks, and Productivity. AI contains distinct Metrics and Orchestrator leaves so usage/account work and session/control work remain understandable without changing their separate port 8787 and 8790 trust boundaries. Tasks and Productivity are separate routes served by the Windows-local Orchestrator; Productivity reads and creates canonical Work Items instead of defining another organizer.
Tasks and Productivity now consume one route-scoped 14/12/10 typography contract: ordinary body text is 14px, persistent secondary and instructional copy is at least 12px, and 10px is restricted to a reviewed registry of eyebrows, IDs, short counts, state/color labels, and timer microcopy. Ordinary desktop controls remain at least 40px and primary/coarse targets remain at least 44px. SortableJS is a same-origin, locally pinned dynamic dependency requested only when a Tasks Kanban list is present; import or constructor failure leaves the existing Alt+Arrow and Move-menu paths available and grants no new task or execution authority.
Task Projects now pairs its desktop inventory with one selected Project cockpit. It reports loaded-only canonical Task/Focus and read-only Session/Room/Automation evidence through exact Project, repository-root, or current-Room relations. Switching the selected card is presentation-only: it sends no request, starts nothing, reserves nothing, and grants no session, Room, lease, automation, repository, or write authority. A missing collection is Not loaded rather than zero, and retained prior evidence remains visibly stale.
The local-first controller hierarchy keeps This PC, Needs You, AI Sessions, Projects & Worktrees, and Automations in the primary navigation. AI Sessions opens to Managed, with Found on this PC and Queue beside it. Codex/Claude Cloud, Other computers, Connectors, History, and System details remain available under Advanced.
Managed sessions now present the authenticated active_recent projection as Current and defer the independent completed_history projection until Show completed history opens. Each page owns its total, cursor, fixed snapshot, empty copy, and stale/read-only state. While its cursor remains, that page always discloses loaded-only search scope and renders its own disabled, visibly busy Load-more control before awaiting the continuation. The authenticated DTO is accepted only after exact bounded row/nested-shape, fixed membership, sibling/cumulative uniqueness, and snapshot/total consistency checks; a null cursor requires cumulative unique loaded count to equal total, while a non-null cursor requires fewer loaded rows than total. Commits and cleanup also require the captured registry, reset epoch, generation, and controller custody to remain current. A null, zero, or negative completion time keeps a terminal record in Current with an explicit warning, and bootstrap sessions do not populate either page. The fixture covers more than 100 rows in both views, independent notices and continuation requests, per-view busy state and coarse-pointer 44-pixel targets, the deferred disclosure, nonpositive-completion warning placement, 390×844 containment, and zero provider calls/effects; real provider, device, assistive-technology, and production behavior remain not verified by that gate.
Each route requests only the controller resources it owns. This PC derives its bounded status from local sessions, Attention, dispatch, lane readiness, and broker health; Cloud, remote-host, and connector failures cannot make that local summary unhealthy. This is a presentation and request-isolation contract, not new provider, credential, host, connector, or mutation authority.
Protected controller resources now expose six truthful phases: loading, unpaired, unavailable, loaded-empty, loaded, and stale. Counts show Not loaded rather than zero until an authenticated collection validates; ordinary empty copy appears only for a valid authenticated empty result. This PC withholds dependent content only when required local evidence is unreadable; stale and loaded-prior refreshing evidence remains visibly aged and read-only. Hosts retains healthy local host inventory while each unreadable remote-host, remote-session, or remote-writer resource gates only its own subsection. Stale rows cannot enable session-derived Tools & Memory or metadata/reconciliation controls, request, queued-work, connector, or computer mutations. Security resets clear pending protected announcements/messages and invalidate reset-sensitive reads and direct activation continuations. Audit/History is an independently tracked protected resource.
Other computers leads with enrolled-host truth: friendly name, current online/offline/trust-pending/stale state, last-seen age, and managed/observed session counts only when their owning resource is current and the exact confirmed host (plus the remote descriptor for observed counts) is online. Missing, offline, trust-pending, malformed, or stale counts read Not loaded; a newly loaded collection cannot make persisted offline inventory current. The host card states whether the exact remote descriptor advertises read-only managed control with approvals never and workspace writes off. Provider-native handoff accepts only a normalized provider HTTPS destination or canonical copy-only resume receipt; copying executes nothing and transfers no Cacheboard authority. Exactly one Add device disclosure separates Phone / private browser pairing from Execution computer enrollment, reusing the existing authenticated forms and endpoints. Each path explains its result and revocation boundary; stale host evidence removes enrollment and visibly disables local mobile-code creation with an adjacent reason. No remote write, approval, generic-shell, provider-credential, host-key, discovery, or new provider-runner authority was added.
The provider-free rendered fixture now verifies that host status precedes setup, one disclosure contains one mobile-create form and one host-enrollment form in the authenticated local case, Enter opens the disclosure, its summary and submit controls measure at least 44 pixels at 390×844, the document does not overflow, and stale host evidence removes enrollment, disables mobile-code creation with adjacent explanatory copy, emits no pairing request, and reports session counts as Not loaded. Static contracts cover forced-colors borders and focus indication, plus positive validated-URL/canonical-copy-only and negative malformed handoff rendering. This is fixture-verified presentation behavior only; it does not verify a live enrolled computer, live pairing, a real phone, provider effects, or assistive-technology output.
Session replacement, browser-session loss, 401, and 403 abort and invalidate protected work and clear protected session, computer, request, queued-work, Cloud, connector, remote-control, and History text before recovery renders. Unpaired recovery returns through the authenticated Dashboard or Start Cacheboard launcher, never Hosts self-pairing. Provider-free rendered coverage verifies these presentation/reset boundaries and zero fixture provider/effect counters; it does not claim a live provider, remote host, real device, screen reader, or production environment.
- Cacheboard has four stable identities and eight provider lanes. It supports many exact chats inside those lanes; it does not add identities dynamically or create unlimited provider capacity.
- Cacheboard does not seize an actively owned Terminal, Desktop, IDE, Claude.ai, ChatGPT, or other consumer client. Observation and native handoff are reported honestly when direct ownership is unavailable.
- Remote managed Claude/Codex control is read-only. Remote approval, shell, and workspace-write authority are unavailable.
- SSH and container connectors are typed observation surfaces, not a generic remote shell or Docker/Kubernetes socket. wmux control is provider-nonnative and grants no provider approval authority.
- Task text, projects, resource links, Focus ranking, memory, and model output are context only. They do not grant session adoption, provider approval, Room membership, worktree ownership, path leases, shell, or write authority.
- P0 Work Items have no permanent purge. Archive and Trash are reversible; only the owner may enter or reactivate Done. Run with AI… opens a confirmation/admission flow rather than executing from task text alone.
- Quick Notes are human-only, reversible archive/no purge, literal text inside Tasks. An active exact note may supply only a title suggestion to the ordinary owner-reviewed Inbox capture gate; it creates no link and leaves the note reusable. Their
context_onlyWork Item links grant no provider, filesystem, execution, Room, host, approval, or automation authority, and note text is excluded from browser storage and automatic provider prompts. - Productivity timer totals are current-document observations, not durable worklogs, completion claims, or productivity scores. Brain Dump drafts are not browser-storage task state; only successful ordinary Work Item creates persist.
- Fixture/local tests do not prove provider health, identity freshness, deployment, publication, a remote device, a real connector, or live provider effects.
- The historical Docker Codex volume is preserved as sensitive dormant rollback custody. It remains unmounted and is never an implicit fallback or automatic reactivation path; routine cleanup must never use
docker compose -f server/docker-compose.yml down -v. Hosted/multi-user redistribution through owner subscription OAuth profiles is outside the supported boundary.
The authoritative checklist is manual-gates.md. The main groups still requiring owner-approved or environment-specific evidence are:
- refresh exact-version Claude/Codex compatibility evidence, separately observe the current single-writer saved-refresh/signed-snapshot flow when authorized, and complete any remaining live lifecycle controls;
- repeat all-eight activation, external-session adoption, Project Room concurrency, and cross-provider recipe acceptance on the intended current tree when needed;
- exercise browser/machine restart recovery and the remaining 200% zoom, assistive-technology, real forced-colors/contrast, and real-device checks; repeat fixture-covered keyboard, focus-restoration, reduced-motion, and measured-target checks in each intended environment when needed;
- install and exercise a real Windows-to-Linux/macOS host, private-tailnet iPhone controller, and intended SSH/container/wmux targets;
- perform the chosen access-restricted restore drill and bounded secret non-disclosure review;
- approve protected external actions—installation, global configuration, credentials, merge/push, deployment, or cleanup—individually.
Until a gate closes for the exact current environment, label it experimental, fixture-verified, locally verified, observed-only, blocked, or not verified. Never promote source presence to production readiness.
Use the definitions in the documentation index: contract, fixture-verified, locally verified, live-verified, experimental, observed-only, blocked, and not verified. A useful receipt records the date, tree/commit, exact command, environment/identity scope, result, skips, and explicit non-claims.
For implementation work, use DEVELOPMENT.md. For the full dated record, use the verification ledger; do not copy its changing test counts or receipts into this page.