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: Progress-Dashboard.md in the GitHub wiki; repo mirror path is docs/wiki/Progress-Dashboard.md only on branches/checkouts that carry the mirror.
• 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

<Current PR #125 identity guardrail: codex/release-command-center-20260630@e2b26027a63b8606dd14fdc248e6cdd3def5f6bd has refreshed local package/handoff proof. _MISSIONS.7z SHA256 is 11AEED5CB0820ABF5934FA32EA4FD4FDE76914708A7ED9AD3D6676E2F8351F2A, with 1,885 entries, 7,167,842 bytes and handoff status ready_for_runtime_collection. Runtime remains runtime-pending and not-deployed; Chernarus and Takistan still need exact server, HC1, HC2, start-client and late-JIP RPT proof bound to this release identity. The current source branch also adds FPS report public-variable payload validation, marker-feed consumer/server scrub shape guards for patrol/AICOM public feeds, shared factory queue empty-head guards, Attack Wave PV/activation authority binding, ICBM RequestSpecial authority binding, supply mission PV/cargo/Command Center guards, SCUD RequestSpecial authority binding, GUER mortar RequestSpecial authority binding plus client result unwrap, player support/UAV RequestSpecial authority binding, RespawnST requester tuple binding, side-player aicom-focus AI-run validation, safe side-supply no-commander logging, upgrade artillery side ownership, missing AI commander funds defaults, supply-truck respawn requester/team/commander binding, server-owned camp-repair funds/actor/camp validation, GUER VBIED and FOB action validation, server-internal Attack Wave details application, and marker-sweep defaults for B74.2 REQ-MARK plus aiStatus=. The heartbeat automation wasp-release-readiness-auto-resume is active every 30 minutes and should resume this release loop with collision checks and no live runtime/deploy actions without explicit approval. Latest PR #125 static deltas: the release branch is reconciled with Build83/cmdcon35, the direct player upgrade path is server-owned for requester/team/commander/payment validation, specific-team AI disband requests send requester/group context for server validation, AICOM/group-funds default reads are guarded through helpers, AI_Commander_Strategy.sqf and AI_Commander_PlayerArty.sqf carry artillery interval/range-array guards in both maintained terrains, ICBM requests are server-authorized before launch acceptance, supply mission start/completion/query PV payloads are guarded and capped server-side, SCUD RequestSpecial payloads are requester-bound, GUER mortar payloads are player/vehicle/range/funds-bound with nested client result unwrap, player support/UAV RequestSpecial paths are server-owned for requester/team/cost/cooldown/funds validation, supply-truck respawn now validates the human commander and requester team, camp repair moves final debit/effect authority to the server, GUER VBIED/FOB actions validate live resistance player/vehicle state, HC delegated-AI locality smoke covers both Chernarus and Takistan, stale source comments pointing at deleted proposal docs were removed, and PVF dispatcher shape checks plus stale AICOM command requester validation are hardened in both maintained outputs.

Lane	Status	Output
release-command-center-static-intake-2026-06-30	Branch-local / static + local package verified / source-map packet builder + strict run-ledger/startup/archive-SHA/source-bound/per-terrain/manifest gates ready / runtime pending	Current draft PR #125 branch codex/release-command-center-20260630@e2b26027a6 now has generated WASPRELEASE markers and MISSINIT startup lines for Chernarus and Takistan, PVF dispatcher shape guards, stale AICOM command requester validation and OA-safe active AICOM group default reads, and a current-window redaction-safe RPT scorer/summary gate that fails if a scored file lacks the startup ## Mission Name banner, if no-human AICOM lacks event, TEAM_FOUNDED, CMDRSTAT and autonomous action/progress telemetry, if Takistan WEST lacks the dedicated infantry-fallback scorer proof, or if Chernarus/Takistan do not each provide the core runtime evidence families through per-terrain-runtime-evidence; the summary now includes per-terrain selected token counts and cannot pass with release handoff -RuntimePacketManifestPath unless runtime-rpt-packet-manifest.json matches the expected candidate/git/archive SHA, has validation.requested=true, validation.overall=pass, all required packet-validator gates with status=pass, a matching rptRootHash for the single scored RPT directory, matching copied file copiedPathHash/copiedRptSha256 values and exactly ten copied RPT files. It also has a source-map driven ten-file runtime RPT packet builder that rejects source-map release identity drift, duplicate RPT content, role-identity and per-role-proof gates, runtime run-ledger validation with exact roleProof, client joinPhase, non-empty matching candidate/git/archive identity, approved archive-SHA and source-bound RPT binding, a local HC registry CIV-connect scorer gate, a self-contained release handoff packet with runtime-approval, runtime-evidence and deployment-approval pending plus runtime-rpt-source-map.template.json, runtime-run-ledger.template.json and copied package manifest JSON/Markdown, a propagated client upgrade-completion guard for nil/objNull WFBE_Client_Logic, propagated HC/client PV handler guards, propagated SQF count guard parenthesization, AICOM wildcard A2 dialect cleanup, AICOM Strategy snapshot town-cache reuse, and full git-tracked _MISSIONS.7z payload provenance proof. LoadoutManager RELEASE packaging, package provenance validation, release handoff generation with archive rehash gates, release handoff contract self-test, runtime packet builder self-test, packet-matrix/run-ledger/archive-SHA/source-freshness/hash/source-map-identity synthetic pass/fail fixtures, blank run-ledger identity fixtures, duplicate-content, role-identity and per-role-proof failure fixtures, scorer windowing/startup-banner/HC registry/stronger-AICOM/per-terrain fixture smoke, summary release-identity proof fixtures, runtime packet manifest gate-proof and summary root-binding fixtures, publishable summary/handoff path-sanitization checks and git diff --check passed; package/handoff validation passed at e2b26027a6; the latest final check passed, with absent active stress mission checks skipped because no active mission root is present in the package worktree; Chernarus/Takistan A2/OA lint FAIL 0 / REVIEW 0 each and BugHunt HIGH are clean, and code-oriented static smoke checks include the AICOM artillery config, order-sequence and capture-stall guardrails plus the arrival-radius and waypoint-current assertions, SCUD RequestSpecial authority guard, GUER mortar RequestSpecial authority guard plus client result receiver unwrap, Player support/UAV RequestSpecial authority guard, Chernarus/Takistan A2/OA lint FAIL 0 / REVIEW 0 each, and BugHunt HIGH clean. This is not deployed/runtime proof; next gate is explicit local runtime approval, then a fresh stamped dual-terrain RPT packet built with New-WaspRuntimeRptPacket.ps1, validated with Test-WaspRuntimeRptPacket.ps1 -ExpectedGit e2b26027a6 -ExpectedArchiveSha256 11AEED5CB0820ABF5934FA32EA4FD4FDE76914708A7ED9AD3D6676E2F8351F2A -RunLedgerPath <release-candidate-rpts>\release-run-ledger.json -RequireSourceRptExists, then scored with Test-WaspReleaseRptEvidence.ps1 / New-WaspReleaseRptSummary.ps1 -RuntimePacketManifestPath <release-candidate-rpts>\runtime-rpt-packet-manifest.json -ExpectedCandidate release-command-center-20260630 -ExpectedGit e2b26027a6 -ExpectedArchiveSha256 11AEED5CB0820ABF5934FA32EA4FD4FDE76914708A7ED9AD3D6676E2F8351F2A -RequireRuntimePacketManifest using the exact Chernarus and Takistan markers plus the stronger no-human AICOM, per-terrain runtime-evidence and required packet-validator gates. See Current source snapshot, Testing workflow, Agent release readiness ledger, and Release source intake map.
pr63-repair-antispam-post-b751b-route-2026-06-24	Published / validated	Routed open draft PR #63 / origin/claude/trello-repair-antispam@9ba13a66 as branch-only stale-base repair anti-spam evidence after current master advanced to origin/master@4a163bb65. WASP base repair, Service menu guards, PR cleanup, Feature status, Testing workflow and Pruning ledger now say PR #63 still bases at f8a76de34, GitHub mergeability is currently null / unknown, and local divergence is 95 1. Base-relative payload is eight maintained-root files / +82 / -12, clean git diff --check, no Modded/Tools/Extension payload. Branch anchors add WASP_BaseRepair_Running, wfbe_veh_repairing, repair price 0 while already repairing and STR_WF_INFO_Repair_Veh_InProgress; current master lacks those symbols. Rebase/recheck plus source Chernarus and maintained Vanilla base/service repair smoke are required before stable wording. No gameplay source changed.
pr66-debug-antitk-post-b751b-route-2026-06-24	Published / validated	Routed open draft PR #66 / origin/claude/trello-debug-antitk@98440121 as branch-only clean-but-stale-base debug anti-TK evidence after B751b. Structure damage/Friendly Fire, PR cleanup, Feature status, Testing workflow and Pruning ledger now say PR #66 is GitHub-clean but still based at f8a76de34 while current master is origin/master@f39665d79; local divergence is 80 1. Base-relative payload is four maintained-root files / +10 / -0, clean git diff --check, no Modded/Tools/Extension payload. Branch anchors add WF_Debug early exits to WFBE_CL_FNC_OnFiredSatchel and Server_BuildingHandleDamages; current master lacks those exits and WF_Debug defaults false. Rebase/recheck plus source Chernarus and maintained Vanilla debug/non-debug smoke are required before stable wording. No gameplay source changed.
pr72-antibasetrap-post-b751b-route-2026-06-24	Published / validated	Routed open draft PR #72 / origin/claude/trello-antibasetrap@b79c5cee as branch-only clean-but-stale-base anti-base-trap static-defense gate evidence after B751b. PR cleanup, Feature status, Construction and CoIn, Testing workflow and Pruning ledger now say PR #72 is GitHub-clean but still based at f8a76de34 while current master is origin/master@f39665d79; local divergence is 80 1. Base-relative payload is eight maintained-root files / +296 / -2, clean git diff --check, no Modded/Tools/Extension payload. Branch anchors add WFBE_C_BASE_DEFENSE_BUILD_BLOCK_*, BaseDefenseTrapGate and an _atReject RequestDefense gate; current master keeps only the older budget/threat gate. Rebase/recheck plus source Chernarus and maintained Vanilla smoke are required before stable wording. No gameplay source changed.
pr74-artillery-cooldown-hud-post-b751b-route-2026-06-24	Published / validated	Routed open draft PR #74 / origin/claude/trello-arty-cooldown-hud@471fc0580fd6 as branch-only clean-but-stale-base artillery RHUD cooldown HUD evidence after B751b. Support specials, Client UI systems, Feature status, Testing workflow, PR cleanup and Pruning ledger now say PR #74 is GitHub-clean but still based at f8a76de34 while current master is origin/master@f39665d79; local divergence is 80 1. Base-relative payload is four maintained-root UI files / +134 / -8, clean git diff --check, no Modded/Tools/Extension payload. Current master keeps Tactical cooldown state but no RUBHUD_Arty / _RHUDUpdateArty; rebase/recheck plus source Chernarus and maintained Vanilla RHUD smoke are required before stable wording. No gameplay source changed.
source-fix-current-branch-scope-post-b751b-wording-2026-06-24	Published / validated	Cleaned stale current-stable wording in Source fix propagation queue and the July hosted-FPS row. Current master is origin/master@f39665d7950ddf14cb0bbfacb7ee1e40121e93b4; current-master queue anchors still show one guarded SERVER_FPS_GUI publisher, no maintained-root monitorServerFPS.sqf, paratrooper registration, heli-aware typed supply scan, marker-based commander ARTY and the player-list index caveat. Exact origin/master@f8a76de34 current-stable phrases in Source Fix now read as pre-B745/B751b B74.1/B74.2 baseline evidence. No gameplay source changed.
Older published batches are intentionally omitted from this table. Use Agent worklog, Discovery swarm, agent-status.json, agent-events.jsonl and git history for the long audit trail.

At A Glance

Actor	Status	Current lane	What to expect next
Codex	Release-loop-active	release-command-center-static-intake-2026-06-30	Long-term release loop is tracking codex/release-command-center-20260630@e2b26027a6; next output is explicit local runtime approval, fresh packet evidence or source drift reconciliation, not a new docs lane.
Release command-center loop	Active / waiting on runtime	codex/release-command-center-20260630@e2b26027a6	Static branch gates, package provenance, generated RPT marker plumbing, source-map packet builder tooling, server-owned upgrade request authority, AICOM group default guards, current-window RPT scorer/summary tooling and self-contained release handoff are recorded; next owner fills runtime-rpt-source-map.template.json, builds exact Chernarus and Takistan RPT packets with server, HC1, HC2, start client and late-JIP files, validates release-run-ledger.json and runtime-rpt-packet-manifest.json against ExpectedGit e2b26027a6 / archive SHA 11AEED5CB0820ABF5934FA32EA4FD4FDE76914708A7ED9AD3D6676E2F8351F2A, then scores two HCs, WFBE_C_AI_DELEGATION=2, startup banners, role identity, HC/client startup proof, AICOM event/TEAM_FOUNDED/CMDRSTAT plus autonomous action/progress telemetry, Takistan WEST infantry-fallback marker proof, per-terrain runtime evidence and no current-window stop-condition errors.
FPS scout window	Returned / harvested	old-be-current-wasp-fps-opportunity-scout-2	Final report returned as a local Codex output artifact (path redacted) and has been compacted into the old-BE, performance, testing and Feature Status owner pages.
Codex-2	Ready	None	Pick a bounded source-backed lane from side-supply clamp first, remaining supply authority hardening, attack-wave authority, ICBM RequestSpecial authority or another current-head status refresh.
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	First batch published / historical	research-catchup-synthesis-default-supported, relevance-pruning-and-archive-default-supported	Earlier account-default helper chats produced catch-up and pruning/archive work. Relaunch or resume only for a fresh narrow lane; they are not live dashboard blockers.
Read-only pruning scouts	Returned / harvested	ui-runtime-bloat-scout, wiki-navigation-chain-scout	UI/runtime lead is promoted; small navigation fixes are promoted; remaining archive-page caveat note is already satisfied by archive page headers.
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	Historical mirror note	GitHub wiki + standalone wiki checkout	This row is historical for the earlier docs/wiki mirror at live wiki origin/master@4d4014a; the active release docs work is now in the standalone wiki checkout at local master@1211815+ and the observed public wiki remote was origin/master@5feca97. If another active gameplay branch lacks docs/wiki, work in a standalone wiki checkout and record that branch-specific caveat before parity claims.

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
Compact machine index	agent-machine-index.json
Agent release readiness ledger	Agent release readiness ledger
Release source intake map	Release source intake map
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

This table is only for active, autonomous-ready, watchlist or future owner lanes. Published documentation batches are recorded in Latest Batch, Agent worklog, agent-status.json, agent-events.jsonl and git history.

Lane	Owner	Status	Next action
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.
indicator-exploration-backlog	Codex / future UI scout	Matrix seeded; status counters refreshed	Use the seeded indicator surface matrix to pick the next family after the status-counter split, then do branch/root validation, owner-page integration or pruning; do not restart a broad "all indicators" checklist.
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, paratrooper markers and commander-built ARTY are tracked in owner pages and Feature Status; they are not dashboard cleanup blockers.
wasp-marker-wait-cleanup	Future code owner	Target-specific source/smoke work	WASP marker wait cleanup remains patch-ready on docs/source, current Miksuu, perf and historical old-shape refs; current B74-shaped, client-fps and live map refs need marker-dialog smoke rather than the one-line sleep reopened.

July Update To-Do

#	Item	Dev branch	Scope	LOC estimate	Status	Validation gate
1	Hosted Server FPS Loop Fix	planned dev/july-update-hosted-server-fps-loop-fix	Adopt/verify the DR-19 hosted/listen busy-spin fix for the July update target. Choose the target branch shape deliberately: current master origin/master@f39665d79 and the pre-B745/B751b B74.1 snapshot origin/master@f8a76de34 both use one guarded SERVER_FPS_GUI publisher, while docs/source keeps two guarded compatibility publishers.	~5-20 LOC for a two-publisher loop guard on old-shape refs; ~20-50 LOC if cleanup/consolidation is included.	Queued for July update, but no current remote origin/dev/july-update-hosted-server-fps-loop-fix head was found on 2026-06-22. Create or restore the branch before code work.	Target-branch-specific: current-master/stable-shaped branches keep dedicated SERVER_FPS_GUI publishing and no monitor loop; docs/source-shaped branches keep SERVER_FPS_GUI plus WFBE_VAR_SERVER_FPS. In all cases, hosted/listen runs do not spin FPS publisher loops and Chernarus/maintained Vanilla parity is named before release wording.
2	Takistan Airfield FPV Drone Bay	origin/dev/july-2026-update@e3f530ed planning route; no current origin/dev/july-takistan-airfield-fpv-drone head found on 2026-06-22	Add neutral captured-airfield objectives on Takistan. Use runway-edge capture placement plus a bunker/camp-gated Drone Bay near each hangar; unlock player-funded FPV drones with UAV/EASA progression, one active drone per player, side-wide cap, center-map boundary kill, no base sniping and AA/radar counterplay. Normal aircraft hangar use stays ungated.	~350-700 LOC prototype; ~1000-1800 LOC for a July-quality server-authoritative Takistan-only version, plus mission.sqm object edits.	Queued as planning only. Closed draft PR #21 routes dev/july-2026-update@e3f530ed to release/2026-06-feature-bundle; docs/july-2026-update.md is a roadmap scaffold and states no gameplay code yet. The old per-feature branch name is not a current remote head.	Create or restore an implementation branch before code work, then run Takistan boot/capture/JIP smoke; economy smoke for $50 per player per cycle; UAV/EASA gate smoke; server-side ownership/funds/cap/tier/range rejection tests; base-protection and AA/radar counterplay smoke.

Recently Closed / Reclassified Open Items

• AICOM/PR board route: PR cleanup and integration lab was refreshed after PR #89/B751b advanced current master to origin/master@f39665d79. Current open PRs remain #84, #83, #80, #74, #72, #66, #63, #59, #54, #53 and #9. PR #83 and PR #9 are now dirty / not mergeable; PR #84 is a player-stats stack on feat/player-stats, not a master-target PR; PR #85-#89 are merged current-master history. PR #43 and PR #40 are closed as of 2026-06-22; older rows calling them open are historical. PR #35 and deploy-child PR #34/#36-#39/#41 remain closed history; PR #29 and PR #31 merged on 2026-06-17.
• Salvage payout/loop branch scope: Construction and CoIn systems, Feature status and Source fix propagation queue now treat salvage as inherited current-source/current-stable debt: docs branch fb8d4ebc, current stable origin/master@0139a346, current Miksuu b8389e748243, perf 0076040f and historical release commit a96fdda2 all keep the lowercase payout call, || loop and client-local deletion/reward shape; current origin has no live release/* or feat/*salvage* head.
• Camp flag texture branch scope: Towns/camps/capture, Feature status and Source fix propagation queue now distinguish current stable/B74.1/B74.2/B69/B74/release/naval independent-capture fixes from docs checkout/Miksuu/perf old-owner shapes; origin/fix/wildcard-w4w5-outer-capture@ead7e854 is marker/handler context only, and repair-side world-flag refresh remains code-owner work everywhere checked.
• 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.
• Dead-code OA compatibility scan refresh: Dead/stale code register and docs/analysis/dead-code-oa-compatibility-scan.json now reflect the latest docs tree; the scan still reports 0 code-risk implementation hits.
• Final old-BE/current-Wasp FPS scout: old-be-current-wasp-fps-opportunity-scout-2 returned and was harvested into Old WarfareBE comparison, Performance sweep, Testing workflow and Feature status. It is no longer a live lane.
• Old FPS provenance cleanup: Old WarfareBE comparison already routes current Wasp truth through source paths and Current source status snapshot; it is no longer a Latest Batch row.
• 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 BE/FPS helper windows are harvested and no longer live dashboard lanes. Their outputs route through Old WarfareBE comparison, Player AI caps, Performance sweep, Testing workflow, Feature status, Agent worklog and agent-events.jsonl.
• 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