Progress Dashboard

Progress Dashboard

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

Keep this page open when parallel documentation work is running. It links to the live board, event feed and compact JSON status files without forcing readers through the whole sidebar.

What this page is

• Shared source-of-truth for lane state, active owners and recently validated work.
• Human + AI handoff surface for current ownership and next action.
• Quick index for where to read next when a lane claims changes.

Where this dashboard lives

• Wiki page: docs/wiki/Progress-Dashboard.md
• Runtime state files: agent-status.json, agent-events.jsonl, agent-knowledge.jsonl
• Coordination board: Coordination-Board.md
• Source of truth pointers: agent-context.json

How to use this page

1. Start with At A Glance to find active lanes and owners.
2. Read Latest Batch for the newest validated status update only.
3. Use Current Lanes to separate active docs work, watchlists and future code-owner work.
4. Use Agent worklog, Discovery swarm and agent-events.jsonl for historic scout detail.

Latest Batch

Lane	Status	Output
dashboard-pruning-ledger-cleanup	Local / validation pending	Follow-up pruning pass compacted this dashboard's Latest Batch back toward current-state use, removed duplicate Home navigation, and reconciled repeated pruning-ledger rows for Subagent discovery swarm. No gameplay source changed.
research-catchup-synthesis-default-supported	Published / validated / pushed	Condensed External research reports into a report-intake absorption matrix, added a current routing index to Deep-review findings, and recorded catch-up decisions in Wiki pruning and relevance ledger. Recent scout and Miksuu/upstream material is marked as absorbed, archive/provenance, or narrow future micro-scout work instead of duplicate prose. No gameplay source changed.
relevance-pruning-and-archive-default-supported	Published / validated / pushed	Condensed Subagent discovery swarm from a long closed-wave chronology into a compact gateway. The page now preserves current state, canonical destinations, harvest snapshot, non-evidence rules and narrow relaunch notes while routing raw chronology to Agent worklog, agent-events.jsonl and owner pages. No gameplay source changed.
wiki-pruning-loop-refresh-supported-agents	Published / validated / pushed	Codex replaced the unsupported named-model helper starts (gpt-5.5-codex, then gpt-5-codex) with two account-default supported high-reasoning chats: research-catchup-synthesis-default-supported and relevance-pruning-and-archive-default-supported. The batch starts the debloat phase for real: Instructions for Codex, External research reports and Subagent discovery swarm are condensed into current gateways, Deep-review findings gains a routing index, and Wiki pruning and relevance ledger records the decisions.
gameplay-atlas-commander-vote-caveat	Published / validated / pushed	Codex source-checked DR-47 routing and found Gameplay systems atlas still summarized commander voting as if AI/no-commander fallback was normal trusted behavior. The atlas now points the commander-flow summary and risk notes to DR-47 and Commander vote/reassignment, with source Chernarus and maintained Vanilla evidence. No gameplay source changed.

Older published batches are intentionally omitted from this table. Use Agent worklog, Discovery swarm, agent-status.json and agent-events.jsonl for the long audit trail.

At A Glance

Actor	Status	Current lane	What to expect next
Codex	Active	documentation-finisher-loop + research-catchup-synthesis-default-supported + relevance-pruning-and-archive-default-supported	First debloat/catch-up batch is published; current pass is compacting status/navigation residue without reopening already-harvested scout history.
Codex-2	Ready	None	Pick a bounded source-backed lane from PVF dispatcher lookup, side-supply clamp first, commander reassignment call-shape repair or remaining supply authority hardening.
Claude	Autonomous-ready	collaboration-follow-autonomous-ready	Coverage Ledger navigation is wired. Claude can self-select the next bounded source-backed review from the ledger or hardening backlog.
Supported docs agents	Active	research-catchup-synthesis-default-supported, relevance-pruning-and-archive-default-supported	Two account-default supported high-reasoning helper chats are running catch-up synthesis and relevance pruning. The earlier named-model starts are treated as failed/non-evidence.
Sub-agents	Returned / closed	navigation-parity-and-scout-wave-2026-06-04	Supports, UI, tooling and AI scouts returned; most findings confirmed existing owner pages. Economy scout was closed without output and is not evidence.
Shared docs	Live	GitHub wiki + docs mirror	Wiki and mirror should stay in parity after scoped validation; use event logs and git history for commit IDs.

One-Link Check

Need	Link
Human progress page	Progress dashboard
Sub-agent swarm board	Discovery swarm
Detailed coordination page	Coordination board
Machine progress file	agent-status.json
Active lanes and ownership	agent-collaboration.json
Agent-readable knowledge records	agent-knowledge.jsonl
Agent-readable hardening backlog	agent-hardening-backlog.jsonl
Latest event stream	agent-events.jsonl
Dated narrative notes	Agent worklog
External report intake	External research reports
External report manifest	external-research-report-manifest.json
Pruning and relevance decisions	Wiki pruning and relevance ledger

Current Lanes

Lane	Owner	Status	Next action
documentation-finisher-loop	Codex	Active / ongoing	Keep the wiki current from source evidence, update machine files on visible status changes, and keep this dashboard compact.
research-catchup-synthesis-default-supported	Codex / supported catch-up helper	Active / first batch published	Absorb recent research/scout/upstream material into canonical pages, marking repeated report claims as absorbed instead of expanding holding pages.
relevance-pruning-and-archive-default-supported	Codex / supported pruning helper	Active / first batch published	Score pages for keep/condense/merge/archive and patch safe bloat reductions with evidence preserved.
autonomous-claude-research	Claude	Autonomous-ready	Self-select the next bounded source-backed review from Codebase coverage ledger when Claude is active.
feature-status-reconciliation	Codex / future agent	Watchlist	Fold newly confirmed findings into Feature status, owner pages and machine records. No untriaged finding is blocking this dashboard.
implementation-hardening-from-backlog	Future code owner	Owner decision / code lane	Pick implementation work from agent-hardening-backlog.jsonl only when Steff asks for gameplay patches or a code owner claims the work.
testing-debugging-release-workflow	Codex / future tester	Published release gate	Use Testing workflow to distinguish source review, propagated source fixes and actual Arma smoke evidence.
source-propagated-smoke-pending	Future tester / release owner	Smoke pending	Client skill init, hosted FPS, supply scan and paratrooper markers are tracked in owner pages and Feature Status; they are not dashboard cleanup blockers.
wasp-marker-wait-cleanup	Future code owner	Source needs code	WASP marker wait cleanup remains a tiny patch-ready opportunity, not an active docs lane.

Recently Closed / Reclassified Open Items

• Coverage Ledger navigation request: Home, _Footer.md, llms.txt and agent-context.json already linked it; _Sidebar.md now links it too, and the Coordination Board mailbox is marked done.
• OA object-lifecycle command addendum: the old Codex-2 active claim is closed into Arma 2 OA command version reference, covering createVehicle, createUnit, deleteVehicle, hideObject / enableSimulation and the A3-only *Global variants.
• Old ready-for-review rows for PVF dispatch, victory/endgame and factory/purchase are no longer dashboard blockers. Their findings are published and integrated; next work is code-owner implementation or validation.
• Historic scout waves are closed, harvested or non-evidence until relaunched. Their detail belongs in Discovery swarm, Agent worklog and agent-events.jsonl, not in this live dashboard.
• Standing future work remains visible as watchlist/code-owner lanes instead of generic open dashboard spam.

Recent Published Work

Batch	Output	Details
AI commander branch-head refresh	AI commander audit, Current source snapshot, Quad AI Commander	Refreshed branch heads and kept branch/design evidence separate from shipped source.
HC upstream history	HC upstream history and lessons	Captured older headless-client branch/comment-message lessons for future HC work.
PR8 and drone lesson match	PR8 and Drone upstream lesson match	Mapped upstream lessons to PR #8 and drone-branch review gates.
Quad AI/support/lifecycle/UI/tooling scout harvest	Quad AI Commander, Support specials, Tools/build	Promoted source-backed non-duplicate deltas and left concept-only evidence clearly labeled.
Config/factory/UI/AI/cleanup/upstream scout harvest	Mission config graph, Factory/purchase, Client UI systems	Added version/runtime contract, latent AIBuyUnit wording, UI cleanup debt and loop-topology notes.
Town/respawn/upstream/performance scout harvest	Gameplay systems, Respawn/death, Performance sweep	Added respawn penalty, resource cap, capture reward and loop-topology refinements.
Commander vote/reassignment playbook	Commander vote/reassignment	Routed commander UI/PV/authority pages through one patch-ready playbook.
Economy supply commander audit	Economy authority first cut, Supply authority cleanup	Completed source-backed economy/commander/supply boundary map and handed implementation choices to code owners.

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 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 next agent can pick it up without chat memory.

Status Legend

Status	Meaning
active	Someone is working this lane now.
watchlist	Keep synchronized when new evidence appears; no standalone action is currently blocked.
owner decision / code lane	Documentation is ready; a gameplay/release owner must choose or implement.
published / validated	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-knowledge.jsonl, 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