Belonging Through Shared Enemy

A simple explanation

Some belonging is built on what the group is for. Some belonging is built on what the group is against. The second kind feels like the first for a long time, because the Belonging System, scanning a room of people who share your antagonism, registers immediate recognition. They hate what I hate. The signal is fast, hot, and almost free.

But the recognition runs in a peculiar direction. The members are connected, in the felt-sense, to the enemy — not to each other. The antagonism is the substance. Remove the enemy, and the architecture collapses. This is why outrage communities can be intensely cohesive while their members, individually, remain unknown to one another for years.

The density signature is false_progress. The loop produces a real-feeling experience of belonging that does not deposit, because the actual deposit channel — specific contact between specific members — is rarely running.

An everyday example

You are six years into following a particular political subreddit, podcast, or commentariat. You can recognise, from a single phrase, whether a writer is on your side. You have a sense of we that has been getting stronger for years. Tomorrow's outrage will come; you will know what to say about it; people in the comments will agree with you and you with them.

You have, in this entire span, met no specific person from this community. You know no member by name. Nobody knows yours. When you imagine the community without its enemy — the rival party loses, the cultural villain retires, the law changes — what you imagine is not relief; it is a strange flatness, as if the room you have been belonging to would no longer have walls.

The recognition was real. The cohesion was real. The deposit channel that would have made these people friends was almost never used.

Why does outrage feel like belonging?

Because shared antagonism is the cheapest and fastest recognition signal humans have. The Belonging System, evolved to read group membership in seconds, registers they hate what I hate faster than almost any other signal — faster than shared values, faster than shared interests, faster than shared experience.

The speed is what makes the loop convincing. Within minutes of encountering an outrage community you feel home. You did not feel this way this fast in the workplace, in the neighbourhood, in the gym. The System, reading the speed, credits depth. The credit is misallocated. The signal was fast because it required no information about the specific others — only confirmation that you all face the same way.

The behavioral loop

A loop that runs daily for years:

1. Trigger — an event surfaces in the news cycle, the forum, the timeline. The enemy has acted again.
2. Group orientation — the tribe, online or offline, faces the same way and produces the same vocabulary. Recognition is registered in seconds.
3. Activation — the System fires a Threat-and-Belonging double signal. The body mobilises; the social signal lights up. We are aligned.
4. Discharge — comment, share, retweet, denounce, mock, dunk. The discharge is felt as participation and registered as belonging-event.
5. Mutual confirmation — others in the tribe perform the same discharge. The recognition compounds. The System logs deposit.
6. No internal deepening — no individual member knows another member better at the end of the day than at the start. The architecture binds member-to-enemy, not member-to-member.
7. Decay and re-fire — within hours the activation drops. The tribe needs the next event to re-fire. The cycle runs again tomorrow, faster, on slimmer triggers.
8. Year-five residue — the chronic activation has become baseline. The world feels darker. Specific contact outside the alignment has thinned. The architecture is intact and the cost is in the body.

Emotional drivers

Four feelings, almost always stacked:

• A genuine moral clarity — the enemy is, in many cases, doing things the member is right to oppose. The clarity is not invented and is not the problem.
• A cohesion-pleasure — the fast warmth of being aligned, which the System reads as belonging deposit and which is real but shallow.
• A chronic activation — the body running a low-grade outrage baseline for years, which becomes its own kind of normal and is rarely noticed.
• A loneliness inside the alignment — the felt-sense, when the screen is down, that nobody from the tribe would notice if you vanished tomorrow, because the binding was never between you and them.

What your nervous system does

The autonomic profile of someone in a sustained shared-enemy loop is distinctive. The sympathetic baseline is elevated — not in dramatic spikes but in a low-grade something is wrong out there that does not down-regulate. Sleep can suffer. Attention narrows toward the news cycle. The parasympathetic settle that ordinary belonging delivers — the felt-sense of I am held by specific people — does not arrive, because the binding is not running between specific people.

Over years the system adapts. The chronic activation becomes baseline. The down-shift required to leave it is large and rarely happens, because every time the activation drops, the next trigger fires. The body holds the cost in sleep, in jaw, in baseline irritability, in a felt-sense that the world is the problem — which, true or not, is also what the architecture requires the member to feel.

The DojoWell interpretation

Belonging through shared enemy is one of the clearest examples of false_progress as a density signature, because the loop is so convincing in the moment and so empty between moments. The original system is belonging. The original ask is let me be in a group whose members recognise me. The substitute is let me share a target with strangers so that the cohesion runs without the contact.

These share a surface property: both feel like being-with. They share none of the underlying deposit channel. Real belonging deposits between encounters because the recognition is between members. Shared-enemy belonging requires re-triggering, because the binding was never inside the group — it was always pointing outward.

Read against the equation: deposit per outrage cycle is near-zero (the cohesion does not survive the trigger); residue is high and chronic (the activation, the narrowed worldview, the loss of relational range); effort is substantial (maintenance of the antagonism, hours of consumption, the metabolic cost of running outraged for years). The verdict is low density. The signature is false_progress — the loop is producing a real-feeling experience and failing to leave a deposit.

This framing matters because the shared-enemy loop is rarely identified by its members. The moral clarity is genuine; the issues are often real; the antagonism, in many cases, is warranted. What is harder to see is that being correct about the enemy does not make the architecture deposit. A correct cause poorly delivered through a shared-enemy loop produces the same residue as a wrong cause delivered the same way.

How do I tell shared values from a shared enemy?

You watch what happens to the group when the enemy is absent.

A group built on shared values continues to function. The members talk to each other. New work begins. Friendships deepen. The same people would meet for the same reasons even if no opponent existed.

A group built on a shared enemy goes quiet. The forum thins. The cohesion drops. The members rediscover that they did not really know each other. This is not a moral failure of the members; it is a structural feature of the architecture. The binding was always external. With no enemy, no binding.

If your community is one whose cohesion would survive the disappearance of its opponent, it is running on values. If it would not, it is running on antagonism. Both can be morally serious; only one deposits.

Practical steps

1. Run the absent-enemy test. Imagine the enemy retiring, losing, dissolving. What would your tribe look like in six months? The answer is the audit.
2. Convert one shared-enemy contact into a specific-person relationship. Reach past the alignment. Ask about something unrelated. Watch whether anything is there.
3. Reduce the outrage intake to a measurable budget. Not abstinence. A budget. The System needs less daily re-firing than the architecture is supplying.
4. Build at least one belonging channel whose membership crosses the enemy line. Not for moral reasons. For relational range. The System needs evidence that contact is possible outside the binding.
5. Notice the loneliness as data. The flatness when the screen goes down is not a personal failing. It is the architecture reporting that the deposit channel between you and the other members has not been used today.

Reflection questions

• If the enemy of your tribe disappeared tomorrow, who in the group would you still know in six months, and who would you?
• How much of your belonging budget is currently paid to alignment-recognition versus to specific-person contact?
• Where has the chronic activation begun to show up in your body, your sleep, your relationships with people outside the alignment?
• What would you have to feel — about the world, about your own correctness, about your stake — to stop needing the enemy to do the binding work?

Frequently Asked Questions