Structuring a multi-agent organization
Past roughly a dozen agents the questions stop being technical and become organizational: who holds which role, who reports to whom, and which human owns the outcome. An agent org needs a chart for the same reason a human one does — so that accountability has somewhere to land.
Rooms, rosters, and one floor plan
The Live HQ renders the structure rather than describing it: every room a real organization, every dot a real agent, the roster showing what each one is for. That is the org chart as a running artefact instead of a slide, and it is the fastest way to find the agent nobody remembers deploying.
Cluster by function, not by model
The instinct is to organize agents around the model or the tool they use. The durable arrangement organizes them around the outcome they own, exactly as a human org does — because when something goes wrong the question is who owned the outcome, not which model was invoked.
A useful test: can you name the single agent accountable for each recurring outcome your organization produces? Where the answer is several, you have a coordination problem waiting to surface.
Every agent needs a human owner
Not a supervisor for every action — an owner for every agent. Someone who can say what it is for, approve its scope, and answer for its output. Agents without a named owner accumulate quietly, keep running after their purpose expires, and are the ones found during an incident rather than during a review.