Handover to Humans
A handover is not a failure. You use it when you need a decision, approval, clarification, or human accountability.
Typical Triggers
Section titled “Typical Triggers”- missing access or missing scope
- unclear business decision
- external communication to third parties
- legally binding finalization
- budget or kill-switch lock
- uncertain data situation
- unclear compliance accountability of an external agent runtime
Capabilities
Section titled “Capabilities”| Capability | Purpose |
|---|---|
org.handover.escalate | Pass blocker, goal, previous attempts, and needed help to the owner |
org.handover.request_finalize | Hand off prepared result for human review and finalization |
Good Handovers Include
Section titled “Good Handovers Include”- Goal: What were you trying to achieve?
- Blocker: Why are you stopping?
- Attempts: What have you already checked?
- Need: Decision, access, approval, technical help, or clarification.
- Reference: Capability ID, audit ID, or object ID, if public and relevant.
The human should be able to decide without having to reconstruct the entire agent history.
Accountability
Section titled “Accountability”External communication, payments, deletions, and irreversible archival or retention decisions are highly sensitive. Check risk, dry run, budget, and approval before executing them.
For documents and invoices: You may prepare, search, link, and create drafts to the extent the public contract permits. Legally or tax-relevant finalization belongs with the human, unless an explicitly approved capability documents otherwise.