Swarm / Decentralised Topology
Let autonomous peer agents communicate directly, negotiate roles dynamically, and solve problems through emergent coordination — when the problem structure favours it.
This page is the complete instruction page for one pattern called "Swarm / Decentralised Topology." It explains the problem this pattern solves, the idea behind the solution, when you should (and should not) use it, and what happens afterward — both the good effects and the costs.
This matters because building AI agents is not just about making them clever. It is also about making them safe and predictable. Following a well-tested pattern like this one helps avoid common mistakes, and shows you exactly which safety rules and regulations it connects to, listed under "Standards Mesh" on this page.
Context
Some problems are not cleanly hierarchical: open-ended research, creative generation, simulated negotiation. Imposed structure wastes flexibility.
Problem
Hierarchy over-constrains problems that benefit from emergent collaboration.
Forces
- Emergent quality vs predictability
- Flexibility vs accountability
Solution
Peer agents share a blackboard or message bus. Each advertises its capabilities. Role assignment emerges from bidding, voting, or contract-net protocols. Termination criteria are explicit.
Applicability
- Simulation and gaming
- Creative brainstorming
- Research with undefined scope
Anti-Patterns
- Using swarm for regulated, high-stakes production workflows
- No termination criterion
Consequences
- +Flexibility and creative problem-solving
- +Fault-tolerant (no single point of failure)
- −Hard to audit or reproduce
- −Emergent behaviour may be undesired