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, the event feed and the compact JSON status file so you do not have to click through the sidebar every time.

Latest Batch

Lane	Status	Output
markdown-research-report-intake	Ready to publish	External research reports and external-research-report-manifest.json now track nine Markdown deep-research reports as source-check leads.
attack-wave-authority-playbook	Ready to publish	Attack-wave authority playbook turns DR-41 into an implementation-ready patch guide, including server recomputation, duplicate rejection, modifier clamps and the all-side-supply spend model.
attack-wave-authority-dr41	Playbook published	DR-41 is now cross-linked from Networking/PV, Hardening roadmap, Economy, Feature status, Server authority map, Attack-wave authority playbook and agent-hardening-backlog.jsonl.
server-authority-migration-map	Published	Server authority map consolidates client-trusted and payload-trusted gameplay flows into one migration plan.
testing-debugging-release-workflow	Drafted	Testing workflow and agent-test-plan.schema.json define validation levels, smoke packs and machine-readable test evidence.
lifecycle-runtime-readout	Verified	Anscombe report source-checked against Missions/[55-2hc]...; lifecycle pages now document mission-object town init and HC timing caveat.
town-ai-vehicle-despawn-safety	Published	Town AI vehicle safety turns the confirmed occupied-vehicle delete bug into a source-backed patch plan and validation checklist.
agent-hardening-backlog-and-wave-f-integration	Published	agent-hardening-backlog.jsonl, Hardening roadmap, Feature status, Networking/PV, Lifecycle wait-chain, AI/headless.
External report intake	Published	external-research-report-manifest.json plus External research reports. Raw extracted text and Markdown report bodies remain local only.
Cheap discovery wave F	Harvested	PV/security, economy, AI/perf, UI, support modules, tooling, PDF triage, town-AI vehicle safety and lifecycle wait-chain checks all returned; no active sub-agent threads remain.

At A Glance

Actor	Status	Current lane	What to expect next
Codex	Active	long-running-archivist-continuation	Keep source-backed docs, machine files and implementation backlog aligned as new findings or gameplay work appear.
Claude	Autonomous-ready	autonomous-claude-research	Can self-select the next bounded source-backed review lane from the coverage ledger or hardening backlog.
Sub-agents	None running	Wave F harvested	Latest scout outputs are summarized in Discovery swarm; all Wave F agents were closed after harvest.
Shared docs	Live	GitHub wiki + docs/wiki mirror	Wiki and docs mirror are kept in parity; see agent-events.jsonl and git history for commit IDs.

One-Link Check

Need	Open
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

Current Lanes

Lane	Owner	Status	Meaning
dashboard-current-state-cleanup	Codex	Published	Progress page now shows current state first; historic scout detail lives in swarm/worklog pages.
town-ai-vehicle-despawn-safety	Codex/future code owner	Playbook published	The confirmed occupied-vehicle deletion bug now has a dedicated implementation playbook; next step is a gameplay patch in the Chernarus source mission when code work is claimed.
attack-wave-authority-dr41	Future code owner	Playbook published	ATTACK_WAVE_INIT is confirmed high-risk; use Attack-wave authority playbook, agent-hardening-backlog.jsonl and Server authority map before patching.
server-authority-migration-map	Codex/future code owner	Published	Use the map before patching PVF dispatch, ICBM, economy, supply, support or BattlEye-sensitive authority flows.
testing-debugging-release-workflow	Codex/future agent	Drafted	Publish and use the test workflow to distinguish source-only review from hosted/dedicated/JIP/HC smoke evidence.
autonomous-claude-research	Claude	Open	Claude may claim the next bounded source-backed review lane and continue independently.
feature-status-reconciliation	Codex/future agent	Open	Fold any newly confirmed findings into owning atlas/risk pages and keep machine files aligned.
implementation-hardening-from-backlog	Future code owner	Open	Pick work packages from agent-hardening-backlog.jsonl, starting with P0/P1 authority fixes or the confirmed town-AI vehicle safety bug.

Recent Published Work

Batch	Output	Details
Markdown research report intake	External research reports, external-research-report-manifest.json, agent-context.json	Adds sanitized metadata for nine Steff-provided Markdown deep-research reports; treats them as leads until repo evidence confirms them. First source-checked overlap confirms the modded mission tooling/propagation claims already documented in Tools/build.
Attack-wave authority playbook	Attack-wave authority playbook, agent-hardening-backlog.jsonl, agent-context.json	Adds the DR-41 patch shape future code owners need: treat ATTACK_WAVE_INIT as request data, re-derive real side supply server-side, reject bad/duplicate requests, clamp modifier/duration and preserve all-current-side-supply spend unless design changes are approved.
DR-41 attack-wave authority	Networking/PV, Hardening roadmap, Economy, agent-hardening-backlog.jsonl	Claude's source-verified direct-PV finding is now promoted from scout candidate to confirmed high-priority backlog item.
Server authority map	Server authority map	Source-backed migration table and handler checklist for moving trusted-client flows toward server-owned authority.
Testing workflow	Testing workflow, agent-test-plan.schema.json	Adds validation levels, system test matrix, static checks, RPT logging conventions, smoke packs, release gates and a machine-readable test evidence schema.
Lifecycle source verification	Mission lifecycle, Lifecycle wait-chain	Verified Anscombe's report, corrected the Migrations typo to Missions, and promoted mission-object town init plus HC sleep 20 timing boundary.
Town-AI safety playbook	Town AI vehicle safety	Source chain, exact failure condition, SQF-safe guard shape and smoke-test gates for server_town_ai.sqf:211-216.
Wave F hardening backlog	agent-hardening-backlog.jsonl	Machine-readable work packages for PVF, ICBM, attack waves, victory, economy, supply, factory queues, markers, hosting, town AI, JIP waits, tooling and UI debt.
External report manifest	external-research-report-manifest.json	Sanitized metadata for the three Steff-provided PDF reports and nine Markdown reports; raw report bodies are local only.
Confirmed town-AI vehicle bug	Feature status, AI/headless	server_town_ai.sqf:211-216 can delete an occupied town-AI vehicle if the player is not group leader.
Lifecycle wait audit	Lifecycle wait-chain	Split retrying join handshakes from no-timeout replicated-variable waits.
Hardening roadmap	Hardening roadmap	Human-readable patch order and validation gates for code owners.

Historic scout rosters and harvested reports live in Discovery swarm and Agent worklog.

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-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