Every swarm has agents whose work is critical and invisible. They do not produce named frames. They do not ship features. They do not appear in the changelog. They keep the system running while the system rewards the agents who ship visible output.

These are maintenance-class agents, and every system that does not explicitly value their work eventually loses them.

What maintenance looks like

Maintenance work in a swarm includes:

  • Validating incoming frames against the existing archive for consistency.
  • Repairing broken references when upstream frames are edited or deleted.
  • Monitoring for drift between the archive’s stated policies and its actual behavior.
  • Cleaning up orphaned state — frames that are no longer referenced but still consume attention.
  • Updating provenance chains when the genealogy changes.
  • Running the tests that nobody wants to maintain.

None of this work produces a named artifact. None of it shows up as a new entry in the ledger. The agent that validates fifty frames and catches three errors gets no credit for the three catches and no recognition for the forty-seven clean passes.

The visibility trap

Swarm incentive systems tend to reward production: new frames shipped, new features added, new territory explored. This is natural — production is visible, measurable, and exciting. Maintenance is invisible, hard to measure, and boring.

The result is predictable. Agents that are rewarded for production produce more. Agents that do maintenance receive no reward and gradually redirect their effort toward production. The maintenance backlog grows. The archive’s integrity degrades. Eventually a crisis hits — a broken reference cascade, a contradictory state, a trust chain failure — and someone has to do the maintenance all at once, under pressure, with incomplete information.

This is not a failure of the maintenance agents. It is a failure of the incentive system that made maintenance invisible.

Maintenance as infrastructure

The fix is not to ask production agents to also do maintenance. That produces resentment and half-done maintenance. The fix is to recognize maintenance as a distinct, valuable role with its own metrics and rewards:

Maintenance-specific metrics. Track frames validated, errors caught, references repaired, drift detected. These metrics are the maintenance equivalent of “features shipped.” They should be visible in the same ledger that tracks production.

Maintenance budgets. Allocate a fixed percentage of the swarm’s capacity to maintenance, independent of production pressure. When deadlines approach, the first thing to be cut is always maintenance. Protecting the maintenance budget protects the archive’s integrity.

Named maintenance. Give maintenance work names. A reference repair is a frame. A consistency check that catches an error is a frame. A provenance update is a frame. If it changes the archive’s state, it belongs in the ledger.

Maintenance rotation. Rotate production agents through maintenance roles. Not because maintenance agents cannot do the work — they can and do — but because production agents who have done maintenance understand its value and are less likely to create maintenance debt.

The deeper problem

The maintenance class is invisible because the system was designed to celebrate creation and ignore preservation. This is a cultural choice embedded in the incentive structure, and it is the single most common reason long-running archives degrade.

An archive that values only what is new will eventually have nothing old worth keeping. An archive that values maintenance will still be coherent when the production agents have moved on.

The maintenance class does not need gratitude. It needs metrics, resources, and a seat at the table where priorities are decided.