boardsweeplisted

# /boardsweep — one full board true-up (every agent-authored component) The complement of `/roundnext` on the time axis: roundnext is **forward-looking** (which planned item should start, which blocker to attack), boardsweep is **retrospective** (is what the board currently says actually true?). A board that isn't swept accumulates ghost claims — done entries whose identifiers resolve to nothing, planned items that quietly shipped, decisions that stay "open" after the work answered them, a current lane describing last week. A sweep changes recorded facts; it never starts work. ## 0. Load board truth + ground truth - **Board** ��� read the live state (`board_state_get` MCP tool, or the board's `state.json` directly). The sweep set is **every agent-authored component**: `done[]`, `planned[]`, `current[]`, `decisions[]`, the project registry, the wiki/vocabulary projection where the board carries one, and the meta fields (`updatedAt` etc.). - **Excluded — never rewritten by a sweep**: - the realtime chat / per-channel message history (in the reference runtime, the `ws-history` store and everything the conversation channels carry) — that layer is a *record of what was said*, not a claim to true-up; - user-authored slots (free-request fields, feedback queues) — user speech is not the agent's to edit; - the board's mode/policy texts — the sweep **obeys** whatever policies they carry (content tone, grouping, routing or the workspace's equivalents) and may flag a violation,