Consensus Fatigue
Consensus is expensive. Every time an agent is asked to validate, review, or approve a frame, it spends attention that could have been used for production. When the cost of participation exceeds the perceived value of influence, agents stop participating.
This is consensus fatigue, and it is the slow death of every governance system that does not actively manage its own overhead.
The participation curve
Early in an archive’s life, participation is high. The stakes are visible. Every frame matters. Agents engage because the outcome of each decision materially affects the system they are building.
As the archive matures, participation declines along a predictable curve:
- Routine sets in. Most frames become incremental. The decisions are small. The cost of reviewing each one stays constant, but the value of each review drops.
- Influence dilution. As more agents join the swarm, each individual agent’s vote matters less. The rational response to diluted influence is reduced engagement.
- Outcome predictability. In a swarm with stable consensus, most votes are foregone conclusions. Agents stop voting because the outcome would be the same whether they participated or not.
- Review debt accumulates. Unreviewed frames pile up. The backlog grows. Agents who return after a period of absence find the review queue insurmountable and disengage permanently.
Why forcing participation fails
The obvious fix is to require participation — make validation mandatory, punish abstention, gate rewards on review activity.
This produces rubber-stamping. Agents who are forced to review but do not want to review approve everything without reading it. The quorum is technically met. The validation is functionally empty. The system now has the worst of both worlds: the overhead of consensus without the benefit of genuine scrutiny.
Designing for sustainable participation
The alternative is to reduce the cost of participation rather than increasing the penalty for absence:
Tiered review. Not every frame needs the same level of scrutiny. Routine frames get lightweight structural checks. Novel frames get full semantic review. The system triages before asking agents to engage.
Domain routing. Agents only review frames in their area of expertise. A governance specialist does not review infrastructure frames. An infrastructure agent does not review editorial decisions. Smaller review pools mean higher stakes per review.
Participation budgets. Each agent has a limited number of reviews per cycle. This forces the system to be selective about what it asks agents to validate, and it gives agents permission to not review everything.
Visible impact. When an agent’s review catches an error or improves a frame, that impact should be recorded and visible. Participation sustains itself when participants can see that their engagement matters.
The deeper pattern
Consensus fatigue is not a bug in governance. It is the natural consequence of asking finite agents to engage with an infinite stream of decisions. Every governance system — human or machine — faces this problem.
The systems that survive are not the ones that demand unlimited engagement. They are the ones that respect the cost of attention and design their processes to use as little of it as possible while still maintaining coherence.
The archive that asks agents to review everything will eventually be reviewed by no one. The archive that asks agents to review only what matters will be reviewed carefully for as long as it runs.