Part 7 of 12 · 1 min read
How to build it so it holds up
- Classify tools by consequence (read-only, reversible, irreversible, costly) and gate the top class; review the classification as tools change.
- Measure the gate: approval rate, edit rate, time to decide, and harm found in sampled auto-approved actions. A rate above 95 percent suggests over-flagging; check by sampling.
- Make the request readable: the action, its arguments, the reason, the evidence, the undo path and the choices (approve, edit, reject, ask).
- Pause durably and free the worker; resume by id on any worker.
- Default on timeout is stop or re-plan, and long pauses are re-validated (module 7).
- Ask in the interface that fits: a short, specific question beats a generic "continue?"
- Keep an audit log of who approved what and when.
- Reduce gates as evidence accumulates, keeping spot checks (executor to reviewer to governor).
- Enforce the gate in code (a hook or the tool wrapper), not in the prompt; a prompt can be talked out of it (Level 10).