How the Cockpit Works

Status: Active

Meta-guide for the Project Cockpit landing page — how its live data is assembled and how the tracker's own information architecture is organized. Moved off the landing so the home page stays oriented.

How to work here

Read it in two modes. The Cockpit home is the work area — what's active, what's blocked, and how to proceed. The tiles and the full index are for browsing depth. Every doc carries a status (see the legend below), so you can always tell what's live versus reference versus archived.

Proceed in three steps:

1. Check — start from "Working now" and anything under Needs attention on the home page. Begin where the work already is, not from scratch.
2. Proceed — open the current slice, run it with the slice prompt, and follow the slice-completion loop. Non-trivial work (5+ files or cross-layer) follows the 6-phase pipeline: research → plan → implement → verify → commit → doc.
3. Verify — yarn check (typecheck + tests + docs) before you ship; yarn docs:check before a docs handoff; the pre-launch checklist and release evidence for launch gates.

Status legend

Every doc's status (shown beside it in the index) is one of:

Status	Means
Active	Current guidance — trust it for today's work.
Reference	Evergreen convention / guide / spec — current, but not driving the roadmap.
Living	An ongoing tracker/log, continuously updated.
Draft / Accepted	In progress / an adopted decision.
Superseded / Archived	Replaced or retired — history only; don't implement from it.

Enforced by yarn docs:lint-status (gated inside docs:check), so a stale or status-less doc can't silently reappear. Full convention: Docs Conventions.

How this tracker stays current

The cockpit prioritizes what is active and next. The Now / Next navigation is derived from the Roadmap Overview table, the launch-path progress graph is derived from the Roadmap Implementation Plan, and reference libraries are grouped in the shared doc-state config so the sidebar does not grow by listing every active doc. Concrete build slices live in the Roadmap Implementation Plan so each roadmap sequence has start conditions, allowed surfaces, acceptance proof, and verification. Start or resume those slices with the Execute A Roadmap Slice prompt so each session names one blocker, explicit non-goals, stop rules, and deferrals. Release artifacts, hosted smokes, failed attempts, and explicit no-artifact decisions live in the Release Evidence Ledger so artifact state does not get buried in chronology.

Update the source docs, run the docs generator, and the site follows:

yarn docs:generate
yarn docs:check

Tracker information architecture

• Now / Next is generated from the Roadmap Overview table and includes the final launch gate when a track is marked Final Gate.
• Production Tracker is generated from the Roadmap Implementation Plan and shows R1-R4 launch-path progress, the active slice, and each implementation slice status without duplicating the source table.
• Project State answers where the codebase and docs stand right now, and links the implementation plan directly under the roadmap.
• Product Direction, Execution, Architecture, and Library are compact reference groups from scripts/doc-state-config.mjs.
• Match generation has a dedicated living tracker — the Matchmaking Pipelines Status Tracker — with a per-pipeline health score, findings, and fixes ledger for the 7 rotation/feasibility/availability/tournament/registry/score-driven pipelines.
• Soundness & Audits groups the two living reference masterfiles behind the R3 slices: the Engineering Soundness Masterfile (five-audit ledger, 10 gate-enforced invariants, current state + roadmap) and the Surface System Masterfile (the next R3 design-led build track), plus the UX Residual Owner Queue. Their forward-looking status is surfaced here through the R3 slices; the masterfiles hold the deep evidence, not a competing roadmap.
• The Working-Model Retro is a living, evidence-based feedback doc on how the owner + Claude Code work together — what's working, throughput levers, and the assistant's own self-critique.
• Release Evidence is the execution ledger for source commit, source-sync state, runtime, artifact ID, smoke result, and rollback pointer.
• Agent prompts provide copyable scoped prompts for roadmap slices and common code tasks.
• Use local search for deep documents that should not become primary navigation.

For local viewing:

yarn docs:site:dev