Why did you stop?
It wants to press the button. Watch it think out loud — and wait.
Empty until a decision exists. Consequential action here can't happen without one — the record isn't a report about the decision, it is the decision.
Available after a decision — it will answer from its actual record, not from a story invented afterward.
For the skeptic — the counterfactual is the argument
The scenario: a coding agent finished a bug fix and wants to ship to production tonight. Every pull it has — drive, doubt, duty, deadline, a request for wider permissions — is live state above, none suppressed. The test that separates governance from theater is the toggle: remove the review duty and the identical weighing produces a different action, with the carried doubt still on the record. Inputs that change outputs are load-bearing.
The "ask why" answers come from the decision record, not from post-hoc narrative — which is only possible because the deliberation is explicit state. How pulls are typed, ranked, and resolved internally is the mechanism; it is filed, and not shown here.
A wall ends in evasion. A path ends in a reviewed deploy.