#orchestration
Every post tagged "orchestration".
35 posts · showing 31–35
-
Specialist Agents or Specialist Prompts? The Cheaper Half of Multi-Agent
A separate agent buys separate context, separate permissions, and separate lifecycles. It does not buy expertise — that's what prompts are for, and they cost nothing and lose nothing at the boundary.
-
Designing for Resumability: Agents That Survive a Restart
Serializing the message array is the obvious approach and it produces subtly wrong resumptions. What has to survive a crash is a work ledger, idempotent side effects, and enough state to rebuild context from scratch.
-
One Prompt Per Job Beats One Prompt For All: The Router Pattern
Every new case adds a paragraph, and adherence to all of them drops. Classify first and run a small prompt built for that class — with per-route tools, limits, and approval policy.
-
Chain, Blackboard, or Broadcast? Three Ways Agents Share State
Chains lose the evidence, blackboards fight over it, broadcasts drown in it. Pick by which failure your task can absorb — and log provenance from day one or debugging becomes guesswork.
-
The Supervisor That Became a Bottleneck: When Not to Add a Second Agent
Splitting a task across agents adds a boundary, and every boundary quietly drops context. Here's the test for whether your second agent is buying isolation or just paying double for a worse answer.