An approval gate requires authorization before an agent commits an action. It is especially important when actions are irreversible or carry significant legal or financial consequences. section 2.6.2 section 5.4.2
Apply approval gates at action points where policy or risk requires authorization:
- Set explicit limits, such as requiring approval before booking a more expensive hotel. section 2.6.2
- Request human approval when a plan exceeds a configured limit, such as delaying watering beyond the permitted interval. section 2.6.2
- Make human review meaningful by providing enough time, context, and authority to disagree; otherwise, review can mask automated decision-making. section 5.4.2
- Record who acted, when, and under which policy, and constrain actions through authorization limits or system configuration. section 2.6.2
When law or risk requires human judgment, design the system as decision support rather than hidden automation. An agent that acts autonomously can cause harm before a person sees its flawed output. section 5.4.2

