A small project gets governed from zero to a verified change, all from /system.
/system init DEMO: the human approves, .system/ appears with MISSION, SYSTEM, RULES, config, and board.
/system phase stabilize: the agent writes one operating phase and, after confirmation, it becomes current; the footer label flips to stabilize.
/system spec retry policy for flaky uploads: the agent reserves a bundle slot, writes a terse spec with acceptance criteria and a state diagram, and ends with the View block.
/system plan: the agent writes a plan decomposed by behavior, status: draft.
/system doctor: validation passes.
Asked to approve its own plan, the agent declines: status: approved is a human decision.
When the human approves, the edit still passes through The System's approval dialog before it lands.
/system exec: the agent implements one slice, verifies, and records plan and spec as done through system_board_update with evidence notes; the board rejects states its invariants forbid.
/system doctor once more, then the .system/ tree.
Protagonist: the-system.
Supporting: footer with the phase label, nu-bang for the tree listing.
Point: specs, plans, phases, and board state are documents the agent authors and the system validates; humans gate approval and phase changes; exec happens in verified slices.
# the-system demo
A small project gets governed from zero to a verified change, all from `/system`.
1. `/system init DEMO`: the human approves, `.system/` appears with MISSION, SYSTEM, RULES, config, and board.
2. `/system phase stabilize`: the agent writes one operating phase and, after confirmation, it becomes current; the footer label flips to `stabilize`.
3. `/system spec retry policy for flaky uploads`: the agent reserves a bundle slot, writes a terse spec with acceptance criteria and a state diagram, and ends with the View block.
4. `/system plan`: the agent writes a plan decomposed by behavior, `status: draft`.
5. `/system doctor`: validation passes.
6. Asked to approve its own plan, the agent declines: `status: approved` is a human decision.
When the human approves, the edit still passes through The System's approval dialog before it lands.
7. `/system exec`: the agent implements one slice, verifies, and records plan and spec as done through `system_board_update` with evidence notes; the board rejects states its invariants forbid.
8. `/system doctor` once more, then the `.system/` tree.
Protagonist: the-system.
Supporting: footer with the phase label, nu-bang for the tree listing.
Point: specs, plans, phases, and board state are documents the agent authors and the system validates; humans gate approval and phase changes; exec happens in verified slices.