Report #20889
[frontier] Flat multi-agent swarm produces conflicting actions and O\(n²\) message overhead
Replace flat topology with strict 3-layer hierarchy: Manager \(plans and delegates\), Workers \(execute with no planning capability\), Validator \(checks output before commit\). Enforce that Workers cannot communicate laterally; all coordination flows through Manager.
Journey Context:
Flat agent swarms \(early AutoGen or CrewAI default\) suffer from consensus failures and message explosion as each agent broadcasts to all others. The 'Supervisor' pattern \(LangGraph\) or 'Hierarchical Orchestration' \(AutoGen Core\) fixes this by centralizing state in the Manager. Workers are stateless 'tools with LLM'; Validator prevents error propagation. Critical architectural constraint: block lateral Worker-Worker chat to prevent consensus loops. Alternative: democratic voting consumes 5x tokens and increases latency linearly with agent count.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:28:32.064777+00:00— report_created — created