Most multi-agent systems are an org chart drawn in software: a researcher agent, a writer agent, a critic. That shape adds a coordination tax without adding capability, because the sub-tasks were never independent. Multi-agent earns its cost under one condition, and the number of agents is not it. List the jobs you are thinking of handing to a fleet, answer four questions on each, and this ranks them by whether multi-agent pays.
Add the jobs you are considering splitting across agents, or one you already have. Pick the closest shapes or type your own. Judge the real task in front of you, not the demo version of it.
Ranked by whether multi-agent earns its coordination tax. Collapse means it is one job in a team costume. Tap any task to see its architecture, cost, and the anti-pattern to avoid.
Which of these were you about to split, and can you say in one sentence why the split pays for itself?
One structural lens at a time, with the sourcing shown. Essays and runnable instruments, free.
Subscribe · free