Checked August 2026
Agent architecture switchyard
Route the same work through six agent topologies
Agent architecture decides where control lives, which contexts are shared or isolated, how work can run in parallel, and where messages cross a boundary. More agents do not automatically produce a better system.
Keep the teaching workload fixed while switching topology. The simulator counts the labeled model nodes, longest sequential chain, explicit messages, and isolated contexts—without inventing a universal quality score.
- Six patterns
- Single · router · fan-out · orchestrator · evaluator · handoff
- Exact counts
- Calls · critical depth · messages · contexts
- Not predicted
- Quality · latency · price
Exact counts for the labeled teaching graph above, assuming one model call per node. They are structural counts—not quality, latency, or price predictions.
Primary research
Inspect the mechanism at its source.
Project architecture and terminology were checked against official documentation on August 10, 2026. Research papers are linked to their original publication records.