Template
Multi-Agent Handoff
Show ownership transfer between agents with payload, status, and next action.
Use
Workflow Guidance
Use when work moves from one specialist agent to another or parallel agents converge.
Human Control
Users can see sender, receiver, carried context, omitted context, and current owner.
What Can Fail
The receiving agent lacks context, duplicates work, or users cannot tell who owns the task.
Recovery Behavior
Keep the handoff packet inspectable and require acceptance before downstream work starts.
State Matrix
Required States
A template is only useful when it shows normal, blocked, and recovery states.
State Coverage
User sees
System does
User sees
System does
User sees
System does
| State | User Sees | System Does |
|---|---|---|
| Prepared | Sender, receiver, payload, and omitted context. | Bundles context into a handoff packet. |
| Accepted | New owner and current task. | Transfers execution state. |
| Rejected | Reason and missing context. | Returns work to the sender or asks for input. |
Implementation
Pattern Pieces
Templates are guidance; registry items stay smaller so teams can compose them into their own product surface.
| Element | Spec |
|---|---|
| Handoff Packet | An ownership-transfer surface for multi-agent workflows with sender, receiver, payload, source basis, receiver action, and recovery path. |
| Run Trace | A dense operational trace for background runs with source touches, status, warnings, timing metadata, and expandable recovery detail. |
| Agent Status Table | A rich operational table for multiple agents with status, active task, progress, confidence, cost, and last activity. |
- ApprovalRisky external actions use a Decision Surface before execution.
- ProvenanceSources, memory, cost, and owner metadata stay visible at the decision point.
- RecoveryBlocked states expose the next input needed instead of showing indefinite activity.