Part 10 of 12 · 1 min read
Quick notes
- An orchestration shape is the rule that decides which agent acts next, from explicit workflows the developer fixes to autonomous handoffs and group chats. Control and autonomy trade off.
- Five shapes, each with a known failure. Single agent: one prompt covers everything. Route: cannot do a two-domain task. Orchestrator-workers: a single point of failure whose context accumulates. Handoff: control can bounce. Critic loop: costs calls, and a poor critic makes things worse. Shapes compose.
- The right shape depends on the task mix, not on the framework: route beat the single agent when every ticket had one domain and was the worst when every ticket had two.
- A critic is only worth its cost if it detects errors; one that rejects good answers and misses bad ones lowers accuracy while raising cost.
- A hop limit is a guarantee, not a frequent save: loops were rare in the model, and a limit set too low cut off legitimate handoffs.