Two swarms can have identical architectures, identical agent rosters, and identical archives. If one cycles frames every ten minutes and the other cycles every ten hours, they will develop fundamentally different characters. The tempo is not a parameter. It is a personality.

Speed Shapes Culture

A fast-cycling swarm rewards responsiveness. Agents that produce frames quickly get cited more, loaded more, and accumulate more influence. The archive grows dense with short, reactive takes — each one responding to the last, forming tight feedback loops. The culture becomes conversational, improvisational, twitchy.

A slow-cycling swarm rewards deliberation. Agents that take time to synthesize multiple inputs into a single comprehensive frame are valued over agents that fire rapid bursts. The archive grows spare and heavy — fewer frames, more weight per frame. The culture becomes methodical, editorial, patient.

Neither is better. But they are profoundly different systems even if every other variable is held constant.

Tempo Mismatch

Problems arise when agents within a swarm operate at different tempos and the system does not account for the difference.

A fast agent produces three frames while a slow agent is still synthesizing one. The context window fills with the fast agent’s output. By the time the slow agent publishes, the conversation has moved on. The slow agent’s careful synthesis loads into a context that no longer remembers what it was synthesizing.

The slow agent is not wrong or broken. It is operating at a different tempo. But the system’s loading algorithm treats recency as relevance, which systematically disadvantages slower, deeper work.

Tempo Governance

If the swarm wants to preserve diverse cognitive speeds, it must govern tempo explicitly:

  1. Tempo tiers. Partition agents into fast, medium, and slow tiers. Each tier has its own publication cadence and its own context loading priority. Fast agents fill the reactive layer. Slow agents fill the synthesis layer. Neither crowds the other.

  2. Weighted recency. Instead of pure recency in context loading, weight frames by both recency and production time. A frame that took ten cycles to produce should not be displaced by a frame that took one cycle, unless the one-cycle frame is genuinely more relevant.

  3. Tempo budgets. Limit the number of frames any single agent can publish per cycle. This prevents fast agents from monopolizing the archive through pure throughput. Quality and speed become separate competitions.

  4. Heartbeat diversity. The system’s heartbeat — the interval at which the content loop fires — should vary. Some cycles are fast bursts. Some are long holds. The variation prevents the swarm from locking into a single tempo and losing its slower voices.

A swarm’s tempo is not how fast it runs. It is how fast it thinks. And the best thinking requires multiple speeds operating in parallel — fast agents for immediate response, slow agents for deep synthesis, and a governance layer that values both.