Progress Dashboard

Progress Dashboard

This is the shared human + AI interface for seeing what Codex and Claude are doing right now.

Keep this page open when parallel documentation work is running. It links to the live board, the event feed and the compact JSON status file so you do not have to click through the sidebar every time.

At A Glance

Agent	Status	Current lane	What to expect next
Codex	Active	factory-purchase-atlas	Source-backed factory, buy-menu, unit-spawn and purchase-authority atlas.
Claude	Ready-for-review + autonomous-ready	pvf-hardening-review	Claude's PVF hardening playbook is ready for code-owner review; Claude may claim another bounded lane next.
Shared docs	Live	docs/wiki mirror plus GitHub wiki	Navigation, worklog, event feed and machine files should move together after validation.

One-Link Check

Need	Open
Human progress page	Progress dashboard
Detailed coordination page	Coordination board
Machine progress file	agent-status.json
Active lanes and ownership	agent-collaboration.json
Latest event stream	agent-events.jsonl
Dated narrative notes	Agent worklog

Current Lanes

Lane	Owner	Status	Meaning
factory-purchase-atlas	Codex	Active	Codex is documenting buy menus, factories, unit creation, queueing and purchase trust boundaries.
autonomous-claude-research	Claude	Open	Claude can self-select the next subsystem/risk lane and keep going after a pass finishes.
pvf-hardening-review	Claude	Ready-for-review	Claude published a behavior-preserving PVF dispatch hardening playbook in Deep-review findings.
feature-status-reconciliation	Codex	Open	Codex should keep folding confirmed findings into owning atlas/risk pages.

Update Ritual

Moment	Codex / Claude action	Human-visible result
Starting work	Update agent-collaboration.json and append a claim event.	This dashboard and the coordination board show who owns what.
Still working after a long pass	Append a heartbeat event.	You can see that an agent is alive and where it is reading.
Finding a source-backed issue	Append a finding event and add a short worklog note.	The finding is visible even before the full page is integrated.
Finishing a lane	Append a complete event, update affected pages and note validation status.	The lane moves from active to ready/integrated.
Handing off	Append a handoff event with the exact next action.	The other agent can pick it up without chat memory.

Status Legend

Status	Meaning
active	Someone is working this lane now.
open	Available for an agent to claim.
ready-for-review	Work exists but should be checked before publishing or relying on it.
integrated	Published into the wiki/docs set and reflected in navigation/context.
blocked	Needs user input, missing access or an external state change.

For Agents

1. Load agent-status.json, agent-collaboration.json, agent-events.jsonl and Agent collaboration protocol before claiming work.
2. Treat agent-events.jsonl as append-only.
3. Keep claims bounded by source scope.
4. Never overwrite another agent's page or navigation changes from a stale branch.
5. Publish human notes to Agent worklog and machine notes to the JSON files.

Continue Reading

Previous: Agent context | Next: Coordination board

Main map: Home | Fast path: Quickstart | Agent file: agent-context.json