#orchestration
Every post tagged "orchestration".
35 posts · showing 11–20
-
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.
-
Let the Model Pick the Transition, Not the Tool
A returns agent that can issue a refund before it has checked eligibility will eventually do exactly that, and no amount of prompt wording reliably stops it. Making the call unavailable is a design decision, not a prompt one.
-
Where Should the Agent Loop Live? Framework, Job Queue, or Workflow Engine
The choice isn't about which framework has the nicer API. It's about what a crash at step six costs — and durable execution engines carry a constraint that fights the way agents are written.
-
The Supervisor That Should Have Been a For-Loop
Every night the same plan, a model call per dispatch, and about once a week it checked eleven services instead of twelve. A for-loop cannot skip an item; an agent orchestrating one eventually will.
-
Designing an Agent You Can Redirect Mid-Run
Twelve files into forty, you realize the approach is wrong. Let it finish or kill it — both bad, and the third option had to be designed in before the run started.
-
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.
-
What Distributed-Systems Experience Transfers to Agent Loops
An agent run is a distributed system with unreliable participants, so most of the discipline transfers. Four things twist — and one microservice instinct actively hurts, because agent boundaries are lossy.
-
The Loop Decisions You Only Make Once
Most agent design choices are cheap to revise. Six aren't — and in every case the answer that ages well is the same one, for the same reason.
-
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.