Handoffs & A2H
A2H (agent-to-human) handoffs are first-class: when policy requires approval or confidence is low, the agent opens an obligation with a deadline and an evidence pack — not a chat message that disappears.
Loop
- Agent proposes action (
crew.ActionProposed/ handoff request). - Obligation recorded (who, what, deadline).
- Human approves, rejects, or amends with reasons.
- Agent resumes from events, not process memory.
- Satisfaction/closure is itself a fact.
Rules
- Deadlines create operational urgency without silent auto-approve (unless policy explicitly says so).
- Evidence packs must be redaction-safe for the audience.
- Handoffs are not a bypass of Gatekeeper for infra mutate.