Approval Gates for Autonomous AI Work
Name the actions that should wait for a human decision.
Gate specific actions
“Be careful” does not define a boundary. “Request explicit approval before deploying, deleting user data, or sending external messages” identifies recognizable actions.
Distinguish preparation from execution
Preparing a draft email can be authorized while sending it remains gated. Building and testing a change can be authorized while production deployment remains gated. This keeps useful work moving up to the boundary.
Match the gate to the environment
A site edit may need a publication gate. Research may need gates for paid data access and contacting interviewees. Review defaults for the actual job rather than assuming every run has the same risks.
Handle the stop
Tell the agent to return with the prepared result, validation evidence, the action requiring approval, and any known implications. Do not phrase a gate as permission to execute automatically after a delay.