#handoffs
Every post tagged "handoffs".
14 posts · showing 1–10
-
The Tax Agent's Workers Counted March Twice and Skipped Late June. Make Every Delegation Return the Range It Actually Covered.
Splitting a year of transactions across four workers looks like clean delegation until the merged total is off and every worker reports success. The fix is a coverage contract the supervisor checks before it adds anything up.
-
Your Critic Agent Approves Everything Because It Read the Worker's Reasoning. Starve It of the Argument, Give It Its Own Evidence.
Forward the worker's transcript to your reviewer agent and it will approve nearly everything — anchored by a conclusion it treats as evidence. Here is the information diet, the mutation test, and the disagreement policy that turn a rubber stamp back into a check.
-
"Done" Is Not a Handback: What a Worker Agent Should Actually Return to Its Supervisor
A worker agent reporting "completed" tells its supervisor nothing it can verify. Here is the handback shape that makes a fabricated result catchable by code instead of by a second model's opinion.
-
Blackboard or Mailbox: How Should Three Agents Share What They Learn?
Two agents discover the same fact; a third contradicts both and nobody notices. The shape of your shared state — a common board or point-to-point messages — decides which of those happens.
-
The Worker Agent Reported Success. Where Should the Check Live?
A worker agent's "done" is a sentence, not evidence — and in effectful work the gap between the two is where silent failures live. Three places to put the verification, and the one most teams pick that buys nothing.
-
What Crosses the Handoff: Transcript, Summary, or Contract?
A triage agent spends eleven tool calls finding the bug, then hands off. Passing the transcript ships its dead ends; passing a summary strips the uncertainty. What a typed handoff contract gets right — and the one field teams always forget.
-
Injection That Crosses a Handoff
The fetcher had no write tools and the analyst never saw a web page. The separation held perfectly — and routed the payload around itself, through the one field that carries prose.
-
When a Worker Returns Garbage: Validating at the Handoff
Thirty-nine extracts were fine. The fortieth had every field present, correctly typed, and null — and the supervisor aggregated it, because well-formed looked like correct.
-
The Handoff That Breaks Every Autonomous SDLC Pipeline
Chain agents across the lifecycle and the first handoff fails hardest — because it's the only one whose input isn't a written artifact, and every downstream check verifies against its output rather than the intent.
-
Upgrading One Agent in a System of Six
A contained improvement to one classifier made the supervisor above it drop half its escalations. No error, no failing test — because each agent's own tests passed against its own version.