You Are Not Addicted to Outrage. Your IC Is Addicted to the Fight.

His partner has mentioned it. Gently at first — "you seem agitated after you read the news." Then less gently. Dev understands why. He watches himself from a distance sometimes: the jaw tightening, the aggressive typing, the inability to just put the phone down and go eat breakfast.

He knows it is not good for him. That awareness changes nothing. The next morning, he opens the app again.

From the inside, every part of it feels like Dev. The outrage is Dev. The need to respond is Dev. The three hours of arguing is Dev failing to have self-control. The guilt about it afterward is Dev, too.

That is the Default Perspective: every signal filed under one identity. If both voices are Dev, then the one commanding him to keep scrolling and the one begging him to stop are both his. Fighting the urge means fighting himself. He cannot win a war where he funds both sides.

The IC Perspective offers a different account. One voice is Dev. The other is the Instinctual Core — the primitive survival system running below his conscious mind, firing its alarms and issuing its commands before Dev gets a single rational vote.

The outrage is not Dev. The demand to respond is not Dev. The inability to stop is not Dev failing — it is the IC succeeding at its job. And the IC's job description was written sixty thousand years ago.

The IC User's Guide is a map of what is actually happening beneath Dev's most automatic reactions. Every input — a headline, a tweet, a news alert, a comment from a stranger — enters the Activation Filter at the bottom and travels up. The IC's survival layers sit at the bottom, which means the IC receives every signal first, faster than Dev's conscious mind, and considerably less accurate.

The map is going to light up only the parts that explain Dev's particular trap.

And here is where most people's model of this breaks down. The assumption is that the anger comes from caring — from moral passion, from values deeply held. Dev does care. His values are real.

But the signal that lights up first, faster than any thought about values, is the Pecking Order layer.

The IC monitors rank constantly. Who has status. Who is being shown respect. Who is getting away with what. To the IC, a powerful person acting without consequence is not an abstract political problem — it is a violation of the dominance hierarchy. The order has been disrupted. Rank has been abused. Someone at the top is breaking the rules that protect everyone below, and the IC treats this as a direct threat.

Not a metaphor. Not an abstraction. A survival alarm.

Once the Pecking Order alarm fires, the IC reaches for the weapons it built for exactly this situation.

The IC has nine of them — and for a perceived rank violation, it does not reach for fear or cravings. It reaches for the tools of confrontation: Anger, to drive Dev toward the threat. Hate, to make the adversary feel unambiguously wrong. Demands, to make the response feel not optional but necessary — a compulsion, not a choice.

Filter → IC → weapons → behavior. The complete chain fires. The word for that is a Hijacking. And the behavior it drives is the same behavior the IC used for sixty thousand years when rank was violated: destroy the threat. Defeat the adversary. Restore the right order.

Dev does not type an angry comment. Dev is commanded to type it, by a system that predates language.

In the environment where this alarm was built, "destroy the threat" worked. The bad actor in the tribe was confronted. Order was restored. The IC stood down.

Dev's environment does not work that way. The news cycle is infinite. There are ten more stories behind this one, each as infuriating as the last. Every stranger he defeats in a comment thread is replaced by three more. The injustice he just argued about will still be there tomorrow — unchanged, unresolved, untouched by his argument.

The IC does not know this. It only knows: threat detected, weapon deployed, threat not eliminated, deploy more weapon.

So the alarm escalates. The Anger builds. The Hate deepens. The Demands get louder. And Dev, already in the grip of a survival command that believes his rank is under siege, cannot find the exit.

The IC pays out Pleasure for that moment. One opponent down: status temporarily restored. A shot of "good job, you fought back" — and Dev hits refresh to find the next threat.

The satisfaction is real. The resolution is not. The win on the comment thread did not resolve the underlying alarm, because the underlying alarm is not actually about that one person or that one story. The IC's Pecking Order monitor is scanning a horizon of seven billion people, eight hundred cable news networks, and an infinite social media scroll. The threat can never be fully eliminated. So the alarm can never fully stand down.

That is the engine of this loop: a same-layer reward that satisfies just enough to keep him searching, but never enough to stop the alarm. Not reward confusion — something more like reward addiction. The IC found the fastest available win on the Pecking Order layer. The win never resolves the threat. So it keeps pulling Dev back for more.

The loop runs like this: injustice detected → Pecking Order alarm → Anger + Hate + Demands fire → scroll and argue → brief win → IC pays out → alarm returns louder → scroll more → argue more → feel worse → repeat.

And woven through each cycle, a layer of shame: I know better than this. Why can't I stop? What is wrong with me? That shame lands directly in the Pecking Order layer — now he is not only losing the battle with injustice, he is also a person who cannot control himself. The alarm escalates again.

This is not one loop. It is a loop inside a loop. And here is the unsettling part: it runs identically across nearly every compulsive pattern people think they fight separately. Swap the headline for a bottle, a binge, a shopping cart — the machine is the same. One map, every version of this trap. That is why the IC Solution exists: learn to read the diagram once, and most of what drives human suffering becomes legible.

Dev had tried willpower. App timers. News blackouts. Commitments to his partner. None of it held past the first genuinely outrageous headline.

Here is why. Willpower is a conscious-brain tool. It is finite, effortful, and arrives second — after the IC has already gotten first access to the signal and fired its weapons. By the time Dev's conscious intention to put the phone down has formed, the Anger has already routed through his nervous system. The Demands are already active. The comment is already half-written.

Willpower can hold for a while. But the IC's alarm is continuous, and willpower is not. Eventually the pressure crosses the limit. He was not weak. He was fighting a subconscious survival system with a conscious-brain tool, and the subconscious gets there first every time.

One morning, Dev was in the middle of it — the anger fully activated, the phone in his hand, the comment half-typed — and something shifted. Not a big shift. A half-second of space. And in that space, a strange, quiet awareness: this is not me deciding to argue. Something is commanding me to.

He did not use any of this language yet. He did not know the term Instinctual Core or Pecking Order alarm. He just noticed — for the first time — that the angry voice felt separate from the part of him that was watching it.

That gap is everything. The IC cannot hijack someone who can see it happening.

The next headline landed. The Anger was there — exactly as loud, exactly as urgent, exactly as certain that he needed to respond immediately. None of that changed.

What changed was Dev's relationship to the signal. He noticed it. He named it: that is a Pecking Order alarm. The IC thinks rank is under threat. It is sending Anger and Demands.

He did not argue with the signal. He did not shame himself for having it. He watched it arrive, like watching weather move through. The signal passed through without commanding a behavior.

No response typed. Phone down. Breakfast.

The alarm was still there, quieter, for a few minutes. Then it faded.

The IC is not retrained by fighting it or shaming it. It is retrained the way you retrain any system that has learned a pattern: by consistently refusing to deliver the reward the pattern was built around.

Every time Dev noticed the Anger and Demands and let them pass through without responding — without giving the IC the "destroy the threat" behavior it was commanding — he was running one rep of retraining. The IC had learned: inject outrage → get combat → receive win signal. Now it was learning something new: inject outrage → no combat → no win. The alarm began to fire with less urgency. Then less frequency.

The signal did not disappear. It just stopped being a command.

And then something unexpected happened. With the IC's command lifted, Dev could actually think about what he cared about — and what he wanted to do with that caring.

He still held his values. He still believed in justice. But he found himself moving from the IC's survival response — destroy the adversary, win the argument — toward something the IC never had access to: chosen action. Writing. Organizing. Conversation with people who could actually affect the outcome. Energy directed at things that could change, rather than arguments with strangers who would not.

That is the difference between being commanded and choosing. Same values. Different driver.

As the compulsive loop quieted, the human happiness drives that had been drowned out by the constant alarm started to come back online.

Intrigue returned: he got curious about the systems behind the injustices, not just the outrage about them. Appreciation: he found himself noticing what was good in the world alongside what was wrong. Engagement: he had real conversations instead of performative arguments. Self-improvement: every near-hijack became a rep, a chance to strengthen the separation. Purpose: he stopped asking who can I defeat today? and started asking what can I actually contribute?

Dev still reads the news. He still cares about what is happening. The difference is that he reads it now — from the human side — instead of being pulled into it by a survival system that cannot tell the difference between an injustice on a screen and a predator in the grass.

The outrage was never Dev. It was the signal. Once he could see it, he stopped obeying it. Once he stopped obeying it, the IC could be retrained. Once the IC quieted, the human — the one who actually wanted to do something meaningful about the world — came back online.