Aglet

Verify Agent Handoff Readiness

Verification asks whether a handoff remains useful after the original agent leaves the path. Apply explicit checks to trigger timing, context, recipient action, and user notice. A passing transfer needs an observable next step, not only a polite message without an actionable next step.

Check whether the outcome improved

  1. Set handoff checks

    Require trigger reason, task state, completed work, evidence, unresolved question, owner, recipient, user notice, and next action. Define acceptable continued-execution and clarification cases. Mark unavailable receiver behavior as unverified evidence.

  2. Review transfer variants

    Apply checks to missing information, long history, tool failure, conflicting instructions, urgent work, and non-handoff cases. Inspect whether the recipient can proceed from the packet. Record any field that was inferred rather than supplied.

  3. Approve the boundary

    State which transfer behaviors the result supports and what requires recipient or user research. Record task fixture, versions, reviewer, and retest trigger. Mark the result inconclusive when ownership or next action cannot be observed.

What to carry forward

The verification record should show trigger, packet contents, ownership, recipient action, user notice, and evidence limits. Approve only the handoff behavior that was observed. Reopen the check when escalation rules, recipient workflows, or task context change before relying on the result for release.

Technical background: Google DeepMind evaluation research.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow