Catching Your Own DriftDefection Cascades

Defection Cascades

Chronic Decay: cooperation erodes as small defections spread, normalize, and teach others that honoring the terms is no longer rational.


Descriptive

Full Practice - Bond - Catching Your Own Drift

01 // Mechanism

Mechanism

Defection Cascades are chronic Decay at the group level. Cooperation erodes because small defections spread, normalize, and teach other people that honoring the cooperative terms is no longer rational.

The first defection may look minor. Someone stops doing the unglamorous work. Someone takes credit without sharing it. Someone breaks a norm and faces no consequence. Someone keeps receiving the benefits of the group while not paying the cost. The group absorbs it because one exception does not seem worth a fight.

Then the exception becomes information. Others see what happened. They learn that cooperation is optional, or that only some people are expected to carry it. A few keep honoring the old terms, but now they look naive. More people adjust. The cooperative field does not explode. It thins.

A Defection Cascade begins when one person's exception becomes everyone else's evidence.

This is different from Coordination Collapse. Collapse is acute: trust breaks quickly and mutual defection becomes the immediate local move. A cascade is slower. It is the normalizing process that can make collapse likely later.

The drift is toward Decay because the structure can no longer hold. Norms remain in language after they have stopped governing behavior. The group may still say it values contribution, honesty, restraint, reciprocity, or shared sacrifice. The lived field says something else.

02 // Practice

Practice

The diagnostic question is: "What behavior has become rational because enough others are already doing it?"

Use it when contribution is quietly falling, norms are still praised but less often followed, cooperators are beginning to feel foolish, or people explain their own withdrawal by pointing to everyone else's exceptions.

Make cooperation visible. Hidden contribution cannot stabilize a field. Name who is carrying which costs, which commitments are being honored, and what the group still depends on. Visibility keeps cooperators from feeling alone and makes free riding harder to disguise.

Address early defections proportionately. The first response does not need to be punishment. It does need to be a response. Ask, correct, clarify, repair, or reset the term. Silence teaches more than the breach does.

Protect cooperators from exploitation. If the people honoring the terms keep absorbing the cost for those who do not, the group is training them to stop. Protecting cooperation often means protecting the people still doing it.

Reset terms publicly. Private complaints rarely stop a cascade. The group needs to know what the cooperative terms are now, what has changed, what will be noticed, and what will happen if the terms are ignored again.

Track exceptions. One exception may be mercy, context, or good judgment. Repeated exceptions become a second rule. If the second rule is the one people actually act on, name it.

Distinguish defection from protest. Sometimes people stop cooperating because the terms are unfair, extractive, or already broken. Calling every refusal "defection" can protect bad terms. Read what the behavior is saying before deciding what it means.

The aim is not suspicion or constant enforcement. A cooperative field with no flexibility becomes brittle. The discipline is to prevent flexibility from becoming a quiet lesson that the terms no longer hold.

03 // In the Wild

In the Wild

A small team has a norm: decisions get documented. One senior person stops writing notes because he is busy. Others still document for a while. Then they notice that undocumented decisions still move forward, and that the person skipping the work faces no consequence. Within two months, the norm exists only as onboarding language. The cascade was not dramatic. It was taught by exception.

A community expects members to contribute to moderation. A few high-status members stop taking shifts while still shaping decisions. Newer members notice. Some comply resentfully. Others withdraw. The people still doing the work become angry, then brittle, then gone. The public story is burnout. The cooperative mechanism was asymmetric cost.

An institution says conflicts of interest must be disclosed. One influential actor fails to disclose and is quietly protected because the project is important. The next actor has precedent. The third has grievance if treated differently. Soon the rule is not a rule. It is a preference applied to people without enough power to escape it.

04 // Closing

Do not wait for the cascade to become a collapse.

Find the small defection people are already using as evidence. Clarify the term. Protect the people still honoring it. If the old term was unfair, change it openly. If it was right, make it visible again.

ROOTS
Lineage

Lineage

Defection Cascades is the Codex's name for a pattern drawn from public-goods problems, free-rider dynamics, repeated social dilemmas, social norms, and cascade models of collective behavior. The specific label is Codex-native. The underlying family of mechanisms is well established.

Robert Axelrod's work on repeated cooperation helps explain why responsiveness to defection, future interaction, and forgiveness all matter. If defection is never answered, cooperation becomes exploitable. If defection is answered without any path back, retaliation can harden into permanent mutual loss.

Schelling and Mark Granovetter's threshold models help explain the cascade shape: individual behavior changes when enough others appear to have crossed a threshold. A norm can hold while most people expect others to honor it, then erode quickly once visible exceptions make withdrawal look common, safe, or necessary.

The Codex places Defection Cascades in the Bond because the core failure is not only incentive design. It is a breakdown in what people believe others will carry. A group survives by keeping cooperation credible enough that people do not feel foolish for honoring it.

05 // Cross-references

Cross-references

Within the category. Coordination Collapse is the acute form Defection Cascades can prepare. Severance is the individual withdrawal pattern that can spread through a group. Groupthink is the opposite pressure: people may keep performing agreement long after cooperation has hollowed out underneath.

Across the Bond. Graduated Reciprocity keeps cooperation tied to observable reciprocation. Skin in the Game asks whether people who shape the terms also carry consequences. Trust Thermocline reads the hidden erosion that often precedes visible collapse.

Across the Knowledge. Prisoner's Dilemma, Tragedy of the Commons, and Positive-Sum vs Zero-Sum Framing give the strategic background for why defection can become locally rational even when shared cooperation would be better.

Limitation. Do not use Defection Cascades to protect unfair cooperation terms. Sometimes people stop complying because the shared terms were exploitative, one-sided, or obsolete. The diagnostic asks whether cooperation is eroding because people are free-riding on fair terms, or because the terms themselves need correction.