Operating
Human approvals
Pausing a run for a person, without holding a worker.
Decision context#
A gate renders resolved values — the figures the agent actually computed — beside the source that produced each one. A reviewer approving a refund sees £842.00 and that it came from stripe.getInvoice → amount_due, not a template placeholder.
SLA and escalation#
Gates carry a countdown. A breached SLA is an incident signature of its own, so approvals that routinely expire show up as a pattern rather than as individual stuck runs.
Was this page helpful?