Where a mission can stop — and how it moves

Read it as a path. Ten checks before a session starts — seven stable contract conditions, three guards hardened in operation — a witness and a human gate before anything lands, one exit command whose code depends on durability alone, and a register that sends every incident back into the next contract. The watcher is drawn twice on purpose: what it does today, and the receive–deliver–wake loop that still has to earn activation.

mission path named refusal learning loop next, not active yet

The board has an architect; the tree has executing seats; authority stays human. ChatGPT Work holds the contracts and the board without becoming a silent second writer. Claude Code, Grok Build and Codex CLI execute inside their declared worktrees, under the model and effort the contract names. The watcher carries observations and, later, routes — never permission. And when a ruling is contested, a seat consulted outside the tree — with no execution surface, so with nothing to defend — returns a read that enters the register: never a decision.

The parcels moving through the wires are the work itself — a pipe with nothing in it is a pipe that has stopped. Filled where something runs today, outlined on the path that is drawn but not yet active. Hover or focus a block to isolate its path.