Severance
The Bond captured by Decay: withdrawal from cooperation because vulnerability, repair, or continued trust feels too costly.
Full Practice - Bond - Catching Your Own Drift
Mechanism
Severance is the Bond captured by Decay. You withdraw from cooperation because the cost of vulnerability feels too high, or because you have learned enough about cooperative failure to stop believing cooperation is worth the exposure.
The failure often begins with accurate seeing. Groups do punish dissent. Trust does get exploited. Repair language is often used badly. Good faith can be weaponized. Once you have seen those patterns clearly, the temptation is to make the seeing final: groups always become this, trust is naive, repair is theater, shared work is just another place to be used.
That is the moment Severance enters. Diagnostic clarity stops serving cooperation and becomes an alibi for leaving cooperation behind.
Severance turns seeing the cost into refusing the bond.Exit is not the failure. Sometimes leaving is the honest move. Some groups should be left. Some relationships have reached their boundary. Some actors have used every repair attempt as another chance to extract. The Bond does not demand infinite exposure.
Severance is narrower. It is withdrawal before the terms have been read, or after one breach has been generalized into a theory of all cooperation. The drift is toward Decay because the cooperative structure stops holding. Nothing remains stable enough to repair, test, or continue.
Practice
The diagnostic question is: "Am I leaving because cooperation no longer serves the Range, or because vulnerability now feels intolerable?"
Use it when you find yourself treating every invitation as manipulation, every repair attempt as performance, every group warmth as future capture, or every breach as proof that trust was foolish from the beginning.
Name the actual breach. Severance thrives on global conclusions. What happened? Who did it? In what domain? Under what terms? If the answer is vague, you may be leaving a story rather than a field.
Keep trust domain-specific. A person may be unreliable with deadlines and trustworthy with money. A group may be bad at receiving dissent and good at practical support. Domain specificity prevents one failure from becoming total withdrawal.
Test repair terms before global exit. What acknowledgement, accountability, restitution, changed behavior, or new boundary would make continued cooperation warranted? If no answer exists, exit may be right. If an answer exists but you refuse to name it, Severance may be protecting you from the risk of repair.
Preserve one narrow cooperative channel where warranted. When broad trust is no longer justified, a smaller channel may still be. Narrow cooperation is not naivety. It is a way of refusing both overexposure and total withdrawal.
Watch contempt. Contempt often arrives disguised as insight. "People are like this." "Groups always do this." "They were never serious." Sometimes contempt accurately marks a boundary. Often it numbs the vulnerability that cooperation would require if you stayed available to evidence.
The countermeasure is not forced forgiveness. It is calibrated continuation. Sometimes continuation means staying. Sometimes it means repair under new terms. Sometimes it means clean exit without turning one failed bond into a doctrine against bonds.
In the Wild
A member leaves a movement after watching its leaders mishandle criticism. The exit is warranted. Then the conclusion expands: all movements become hypocrisy, all shared language becomes manipulation, all belonging is a trap. The first judgment may be accurate. The second turns one field's failure into withdrawal from the whole cooperative project.
A team member is repeatedly ignored in planning meetings. She stops contributing, then stops reading the drafts, then stops answering messages except with formal compliance. No one can say she is wrong to feel tired. But the withdrawal has become invisible defection from the work. The question is whether the group needs a boundary, a repair attempt, or an honest exit, not a long quiet disappearance.
A person burned by a breach decides that trust itself was the mistake. Future relationships are kept pleasant and shallow. Nothing can exploit him because nothing can reach him. Severance can produce a very clean life. It can also produce a life where no shared work survives first contact with risk.
Severance asks you to make exit honest.
Leave when leaving is warranted. Set boundaries when boundaries are warranted. But do not let clarity about cooperative failure become a private permission slip to stop cooperating before the evidence has been read.
Lineage
Severance is a Codex-native failure-mode name. Its nearest formal neighbor is Albert Hirschman's exit, voice, and loyalty frame. When members experience decline, they can exit or use voice to improve the system from within; loyalty can delay exit long enough for voice to work. The Codex's concern is what happens when exit becomes the default before voice, repair, boundary-setting, or domain-specific trust has been tested.
Attachment and withdrawal literature helps describe the felt pattern: exposure begins to feel unsafe, so distance becomes the strategy. Trust research and social-capital accounts add the cooperative cost. A society, team, or partnership cannot run on total exposure, but it also cannot run when every actor treats vulnerability as a mistake to be avoided.
The Codex uses Severance as the Bond's Decay-side failure because the person may be right about many specific risks and still wrong about the conclusion. Seeing how cooperation fails is part of the Bond. Letting that seeing end cooperation itself is the drift.
Cross-references
Within the category. Fusion is the opposite discipline-level failure: over-attachment instead of withdrawal. Coordination Collapse can happen when Severance spreads quickly across a group. Defection Cascades are the slower group-level version: more people stop honoring the cooperative terms because they no longer believe others will.
Across the Bond. Trust Repair and Common Knowledge Generation keep repair from becoming private hope. Graduated Reciprocity gives you a way to restart cooperation without overexposure. The Exclusion Problem names the point where boundary or exclusion protects the cooperative system rather than evades the work.
Across the Knowledge. Paralysis is the Knowledge failure where complexity dissolves action. Severance is the Bond failure where relational risk dissolves cooperation.
Limitation. Do not diagnose Severance when exit is warranted. Leaving an abusive, exploitative, or repeatedly bad-faith system can be fidelity to the Range. The diagnostic applies when withdrawal generalizes beyond the evidence, refuses repair or bounded cooperation without reading the terms, or turns the cost of cooperation into a reason to abandon cooperation as such.