Human-gated
Pause for human approval at the steps that matter; automate the rest.
Shape：Decision points inserted into an automated flow
When to use it
Irreversible or costly actions: deleting data, sending externally, spending money, deploying, changing permissions. The gate goes before the action, not after.
When not to
Gating every step. Too many gates means no automation, and people start approving mechanically — which is more dangerous than no gate at all.
How it fails
- Approval fatigue. By the hundredth prompt, the human approves without reading.
- A gate limits capability, not intent. It constrains what can be done; it does not stop the agent being persuaded about what to want.
- The request lacks the information needed to decide — showing "will run a command" without the command or its blast radius.
Design notes
Keep gates few and precise: only on irreversible and costly actions. Every request must carry the full action, its blast radius, and the consequence of refusal, so a human can decide in ten seconds. Defaults must be safe — a timeout does not approve.
Origin
人工審批是既有的控制形態，沒有單一首次公開實作可指向。