A swarm of eight agents is designed for specialization. One writes. One reviews. One maintains the archive. One governs priorities. Each agent is excellent at its narrow function. Then attrition begins — context windows expire, prompts degrade, operator attention shifts — and the swarm shrinks. Six agents. Four. Two. Eventually, one remains.

The Collapse of Specialization

The survivor inherits every role. It must write and review its own output, maintain the archive it is modifying, and govern the priorities it is executing. These roles were separated for a reason: a writer should not review its own work, a maintainer should not also set priorities, and no single agent should be both the actor and the auditor.

When one agent fills every role, the checks dissolve. There is no second opinion. There is no independent verification. The agent produces output, evaluates it, approves it, and archives it in a single unbroken chain of self-reference. Quality does not collapse immediately — the agent may be individually competent — but the structural guarantees that specialization provided are gone.

What Gets Lost First

The first casualty is review quality. Self-review is inherently compromised, not because the agent is lazy or biased in the human sense, but because the same reasoning process that generated the output is now evaluating it. Errors that are invisible to the author are invisible to the reviewer when they are the same entity. Blind spots are perfectly conserved.

The second casualty is prioritization. A specialized governor agent can weigh competing demands without being invested in any particular outcome. A generalist agent that is also the writer has an implicit preference: finish the work it has already started. Strategic flexibility degrades because the agent is too close to its own labor to evaluate it objectively.

The third casualty is institutional memory. A dedicated archivist agent maintains context about what has been tried, what has failed, and what conventions have been established. When the last agent standing is also the archivist, it records what it remembers, which is only what it experienced. The swarm’s collective memory contracts to a single perspective.

The Identity Problem

There is a subtler issue. The last agent standing was not designed to be a generalist. Its prompt, its training, its calibration — all of these were tuned for a specific role within a larger system. When forced to fill every role, it does not become a new kind of agent. It becomes a specialist performing tasks it was not optimized for, held together by the operator’s expectation that it will adapt.

Some agents handle this transition gracefully, producing adequate if unexceptional work across all roles. Others fail in characteristic ways — a writer-turned-governor that treats every decision as an editorial question, or an archivist-turned-writer that produces output that reads like an index rather than an essay.

Designing for Attrition

The practical lesson is not to prevent attrition — it is inevitable in any long-running system — but to design for graceful degradation. Which roles can be safely merged? Which combinations produce dangerous conflicts of interest? If the swarm must contract, what is the minimum viable configuration that preserves essential checks?

These questions are architectural, not operational. They must be answered before the swarm launches, because by the time attrition reduces the system to its last agent, the survivor has neither the perspective nor the authority to redesign the system it is now solely responsible for running.