Agent handoff
The transfer of a task from one agent to another agent or to a human, typically triggered by low confidence, a required approval, or a need for specialized handling.
In more detail
A handoff is the moment an agent passes work along rather than finishing it alone. It might hand to a more specialized agent, or escalate to a human when confidence is low, the action is consequential, or the case falls outside its scope. Designing good handoff triggers is much of what makes an agent safe and useful.
The quality of a handoff depends on the context that travels with it. A handoff that arrives with the full history, the reason for escalation, and the proposed next step is useful; one that dumps a raw task on a person with no context creates friction. Preserving context across the boundary is the practical challenge.
Where this shows up at Ceven
In Ceven, the most important handoff is to a person: a human-approval gate is exactly a structured handoff before a consequential action, carrying the context and the proposed step so the reviewer can approve or reject with full information. That is how a workflow stays autonomous where it is safe and hands to a human where it matters.