Find the consequential decision
Place the gate before a result or action becomes consequential. Review may be needed for uncertain evidence, external communication, or an action that changes another system.
Give reviewers useful context
Present the proposed result, its sources, and the outstanding uncertainty. A reviewer should be able to approve, reject, or request a specific revision without reconstructing the entire run.
A harness makes context, tools, execution, and review part of one observable system.
Make approval a state transition
Waiting is not approval. Record the explicit decision and resume only the appropriate downstream steps. A request for changes should return the task to a defined revision state.
Learn from feedback
Use review outcomes to identify recurring gaps in retrieval, tools, and task definitions. Keep feedback attributable to the specific execution rather than treating every correction as a universal rule.