Coordination Collapse
Decay in the shared expectations that let people rely on one another: a cooperating group fragments when trust evaporates and mutual defection becomes locally rational, in days or over years.
Catching Your Own Drift — Bond
Mechanism
Coordination Collapse is Decay at the group level: a breakdown in the shared expectations that let people rely on one another. A cooperating group fragments because people no longer believe the cooperative terms will hold.
The key word is expectation. Defection Cascades spread withdrawal by example, as observed breaches or unequal burdens change what others are willing to carry. Coordination Collapse spreads by anticipation: each member, expecting the others to pull out, pulls out first. Either can unfold quickly or slowly, and each can feed the other. A bank run can empty a bank in days; a coalition can lose confidence in itself over years. A breach, shock, rumor, leadership failure, scarcity event, deadline crisis, or visible betrayal changes what people think everyone else is about to do. Once that expectation changes, the local rational move changes with it.
People defect because they expect defection. They withhold information because they expect others to withhold. They grab resources because they expect others to grab first. They leave the channel because they believe the channel can no longer support shared decisions or commitments. The collapse is not only private fear. It is fear about what everyone else now believes.
Coordination Collapse begins when cooperation stops looking safe at the same time for enough people.This is why the failure belongs in the Bond. The map may still be accurate. The incentives may even be obvious. What breaks is the cooperative field: trust, communication, common knowledge, shared expectations, and the belief that staying inside the terms will not make you the only one still paying the cost.
The drift is Decay because the structure cannot hold under pressure. The group does not become too rigid. It loses the shared pattern that made joint action possible.
Practice
The diagnostic question is: "What changed so cooperation stopped looking safe to the people involved?"
Use it when a group shifts from shared work to self-protection, when people start acting on rumors about what others will do, or when everyone claims they are only responding to everyone else's loss of trust.
Name the broken expectation. What did people believe would hold that no longer seems to hold? Payment, confidentiality, fairness, shared credit, leadership protection, decision procedure, mutual restraint, continued participation? Collapse often looks chaotic because the broken expectation is unnamed. Then name which commitments can still realistically be kept.
Reopen communication channels. Collapse accelerates when people act from private interpretations. A public channel, even a narrow one, can slow the slide by letting people hear what others are actually doing instead of what they fear others are doing.
Generate common knowledge. Private reassurance is not enough. People need to know not only that terms still exist, but that others know those terms exist and expect them to be honored. Put the state of play where everyone relevant can see it, and keep out what has to stay confidential. Making terms known does not make them fair.
Slow irreversible moves. If possible, pause departures, public accusations, resource grabs, unilateral announcements, or permanent commitments until the group has re-established what is true. The first task is often not repair. It is stopping the collapse from consuming the remaining options. The pause does not extend to urgent protection, to a disclosure people need in order to stay safe, or to a departure someone has good reason to make.
Restart with small reciprocal commitments. Large declarations rarely restore trust during collapse. Small, visible, time-bounded commitments can. Who will do what by when, and what will everyone else see when it is done?
Distinguish panic from opportunism. Some people defect because they are frightened. Some have run out of resources, and some have misread what others are doing. Others use the collapse to extract. Many act from a mix, and often you will not know which. Start from what people did and what risk it creates, and hold the explanation more loosely. Treating all of it as the same creates injustice in both directions.
Coordination Collapse is easiest to prevent before the shock. Redundant communication channels, visible procedures, trusted repair paths, and clear boundaries do not look dramatic when things are calm. They are the reason the group still has something to hold when the calm ends.
In the Wild
A volunteer organization discovers that a treasurer mishandled funds. Before facts are established, rumors spread that the board knew, that donors will leave, that the next event will be canceled, that anyone who stays will be blamed. People resign to protect themselves. Donors freeze support. The event collapses. The original breach was serious. The second failure was expectation collapse.
A product team hits a severe deadline crisis. Leadership goes quiet for two days. Engineers assume priorities have changed, design assumes engineering has stopped committing, customer support starts drafting apology language, and sales begins making private promises to key clients. Nobody is trying to sabotage the work. Everyone is acting sensibly inside a field where shared expectations disappeared.
A community dispute becomes public. Members begin leaving group chats, saving screenshots, forming side channels, and rewriting ambiguous past events as evidence of betrayal. Some boundary-setting may be necessary. But once every move is read as proof of coming defection, the group is no longer deliberating. It is breaking in real time.
When coordination collapses, do not start by demanding trust. Start by making the field legible again.
Name the broken expectation. Put the current terms where people can see them. Slow the irreversible moves. Then ask what small reciprocal act would make cooperation locally rational again.
Why this tool is in the Inheritance. Coordination Collapse belongs in this category because it names the Decay failure of cooperation when shared expectations break. Whether the break takes days or years, self-protection becomes locally rational for many people at once. Defection Cascades cover the spread of withdrawal by example, which can prepare the break; each can feed the other. Common Knowledge Generation helps repair it. Coordination Collapse gives the Inheritance a diagnostic for the moment when the shared field has to be made legible again before trust can be asked for.
Lineage
Coordination Collapse is the Codex's name for a pattern drawn from coordination failure in game theory and economics, repeated social dilemmas, common-knowledge problems, and expectation-driven breakdowns such as bank-run dynamics. The specific label is Codex-native. The underlying mechanism is not.
Thomas Schelling's work on focal points, tipping, and how local expectations produce collective outcomes is central background. Repeated Prisoner's Dilemma research, including Robert Axelrod and W. D. Hamilton's work on the evolution of cooperation, shows why cooperation depends on expectations about future interaction, responsiveness, and the conditions under which defection will be answered or forgiven.
The Codex places Coordination Collapse in the Bond because the failure is not only bad incentives. It is the loss of a shared cooperative field. The remedy therefore includes incentives, but it also includes communication, common knowledge, visible terms, and credible small moves that let people believe the field can hold again.
Cross-references
Within the category. Defection Cascades spread withdrawal by example, as each breach others see lowers the bar for the next; a cascade can prepare a collapse, and a collapse can start a cascade. Severance can spread into Coordination Collapse when enough people withdraw at once. Echo Chambers can make collapse harder to repair by making each side's fear self-confirming.
Across the Bond. Common Knowledge Generation is one direct repair instrument. Trust Thermocline often precedes collapse: trust erodes invisibly and then drops all at once. Schelling Fences can prevent gradual exceptions from setting up the break.
Across Reality. Prisoner's Dilemma, Schelling Points, and Nash Equilibrium give the strategic background: people can land in a worse stable pattern even when better cooperation would be possible.
Limitation. Do not call every conflict Coordination Collapse. The diagnostic requires fragmentation around broken shared expectations, not merely disagreement, low morale, or a hard decision. A group can be in conflict and still be coordinated.