1. Irreversible means expensive to undo
Sending a payment, deleting a record, emailing a customer, merging to the main branch, changing a permission. Those are different risks, and they share a property: undoing them costs more than the draft did. The agent can prepare the draft. A person decides the step.
A blocked action is not permission to take a neighboring one. In the production agents masterclass, a rule that stops a bad payment is not permission to post a good one. A person still approves before money moves. The same shape applies outside finance. The gate is on the action, not on the vibe of the draft.
2. Put the evidence in front of the decision
Human review fails in two boring ways. Approval fatigue: everything is urgent, so everything is approved. Automation bias: the draft looks finished, so the person agrees. The design response is an evidence-first screen. Show the source, the action, and what will change. Hide the essay. Sample the approvals afterward, so you notice when the gate has become a rubber stamp.
The person needs a real choice, including the choice to do nothing. “Leave this process alone” is a valid outcome of a review. A gate with only an Approve button is a delay, not a control.
3. Least privilege before more autonomy
Expand what the agent may do only after the trace, the check, and a named owner exist. Start with suggestions. Promote an action to unattended only when the eval and the incident record say the failure is acceptable. Isolate the execution. A sandbox limits the blast radius of a wrong tool call. It does not make the tool call correct.
Identity sits on the tool, not only on the chat user. The agent acts as some principal. That principal should not be a shared god account. Action-specific authorization means “this run may create a draft refund,” not “this run may do whatever the service account can do.”
4. The law is not a paragraph in the prompt
The EU AI Act is a regulation, and it has been amended since it was adopted. This page is not a reading of it, and it is not legal advice. Counsel tells you which obligations apply. The engineering work that usually sits underneath is the same work you wanted anyway: a purpose, a human decision where the impact is high, a log, and a way to stop.
Security reviews and model-risk reviews are owners, not phases you skip because a pilot is small. A small pilot that writes to a real system is not small.
5. What to put on the gate
List the actions in the workflow. Mark the ones that are expensive to undo. For each, name the person who may approve, what they must see, and what gets logged. If the name is “the agent,” move it back to a person.
You only learn whether the gate is working by measuring the failures: evals and release gates.