name: the-system-board
description: "Use before proposing or updating System board state through system_board_propose or system_board_update."
The System board contract
Board state lives only in .system/board.json at schema version 0.
Specs and plans use todo|done|dropped; issues use open|done|dropped.
Dropped means intentionally excluded, not complete; it is omitted from active counts and unfinished lists.
A spec may be done without plans, but cannot be done while any linked plan is todo.
Dropping a spec leaves its plans unchanged, and dropped plans do not block spec completion.
Reopening a dropped plan to todo demotes a done spec; a dropped spec remains dropped.
Issues never change spec state.
Assessment proposes board changes for human review; it never applies them.
Exec applies verified states directly through system_board_update, recorded with source agent and a terse evidence note.
Claim a state only from verification you ran and read; the human overrides any entry in /system board.
---
name: the-system-board
description: "Use before proposing or updating System board state through system_board_propose or system_board_update."
---
# The System board contract
Board state lives only in `.system/board.json` at schema version 0.
Specs and plans use `todo|done|dropped`; issues use `open|done|dropped`.
Dropped means intentionally excluded, not complete; it is omitted from active counts and unfinished lists.
A spec may be done without plans, but cannot be done while any linked plan is todo.
Dropping a spec leaves its plans unchanged, and dropped plans do not block spec completion.
Reopening a dropped plan to todo demotes a done spec; a dropped spec remains dropped.
Issues never change spec state.
Assessment proposes board changes for human review; it never applies them.
Exec applies verified states directly through `system_board_update`, recorded with source agent and a terse evidence note.
Claim a state only from verification you ran and read; the human overrides any entry in `/system board`.