How to Run an AI Swarm Without Losing Control
A hundred agents do not create leverage by themselves. They create a coordination problem. The operating layer is where the real system begins.
Start with three layers
Goals, source of truth, permissions, definitions of done, evidence requirements, cost rules and human gates. This layer should survive model changes.
The agent products or model runtimes actually executing tasks. These can change frequently. Treat them as replaceable workers, not the company memory.
Browsers, repositories, databases, payment systems, publishing systems, inboxes and production environments where actions have real consequences.
Six controls that matter more than agent count
Why this matters now
Recent AI-agent products increasingly support persistent computers, routines, shared files and parallel Bots. That lowers the cost of building desk-like structures around one operator. The failure mode is predictable: organizations add more agents before defining policy, state and escalation.
The result is “split brain”: two capable agents follow different assumptions, use different sources of truth, or execute incompatible actions.
A minimal operating contract
SOURCE OF TRUTH — Which system wins when data conflicts?
CAN DO — What may the agent execute alone?
MUST ASK — Which actions require approval?
STOP — What conditions halt the workflow?
EVIDENCE — What must be recorded before work counts as complete?
STATE — What must be handed to the next agent or runtime?
The portable part is the asset
Models will keep changing. The durable asset is the operating contract around them: Brain, Policy, Skills and State. If that layer is portable, a company can replace runtimes without rebuilding its operating memory from scratch.
The product link is optional reading for teams that want reusable implementation templates. This article stands on its own. Named AI products are referenced only for compatibility and industry context; Stratum Praxis is independent of those vendors.