The Rage Has to Go Somewhere

Nico is thirty-six years old and good at his job. He manages a logistics team, delivers clean results, and is the kind of person his colleagues go to when something breaks. He is not a reactive person. He very rarely raises his voice.

What he does, reliably, is eat.

Not at mealtimes. Not from hunger. After meetings where his input was glossed over. After calls where someone got the credit for what he had built. After a senior director walked past his ideas twice in one week and praised a junior colleague for a version of them on the third. He never says anything in the room. He walks back to his desk, feels something pressing behind his eyes, and within twenty minutes he is at the kitchen counter eating whatever is in front of him — crackers, cold leftovers, three handfuls of something he cannot taste because he is not actually there.

Afterward he feels worse. He also does it again the next time.

Two voices are in the room when this happens: one that says I need something, right now, and one that says don't react, just walk away. Both feel completely, unmistakably like him.

So he runs an experiment. Not to prove anything — just to try it on. What if the voice sending him to the kitchen is not actually him? What if it is something separate — a survival system that has been running inside him since long before he could think about it — something we call the Instinctual Core?

This is not wishful thinking. It is not a trick he plays on himself. Neither way of seeing is "right" or "wrong" — but holding the IC as separate is the accurate picture, and the more useful one by far. The Instinctual Core runs its own ancient agenda, encoded in genetic code and executed by a subconscious brain that operates completely independently of the conscious Nico. He is not disowning some part of himself; he is accurately naming something that was never him in the first place. That distinction is what makes lasting change possible.

The urge arriving in his body is not his decision. It comes from a separate system, with a separate survival agenda, that got there before he did.

The instant he tries that on — moves from left picture to right — something shifts. He is no longer inside the urge. He is watching it. And a watched urge is no longer a command.

Holding that one idea — maybe the craving is not me — is what unlocks the map.

The IC User's Guide is a diagram of exactly what the Instinctual Core does: why it fires, what it launches, what it wants the body to do. Nico puts what just happened on that map and starts to read it.

He starts with what he can actually feel — the raw signals in his body after that meeting. He breaks them down.

The first one is Anger. Not dramatic, not explosive — a compressed, pressurized version that has nowhere to discharge in a workplace where expressing it would cost him something. A slow burn sitting behind his sternum.

Underneath that: Stress. The kind that does not switch off. The calculating background hum that says something is wrong and you have not fixed it yet. It has been there all afternoon.

Both of these feel like emotions he is having. From the IC perspective, they are something else entirely — weapons, fired at him by a survival system that wants him to act.

Then a third signal arrives: Cravings. Not for any specific food — for something, anything, right now. It lands with urgency. And this is where the story gets specific, because the craving is not coming from hunger. It is coming from the same system that fired the Anger and the Stress. The IC has added a new weapon to the stack — and this is the one that actually drives him to the kitchen.

Three weapons at once: Anger, Stress, Cravings. His body is loaded. This is the IC doing what it does — pushing hard for a specific outcome. The question is what outcome, and why.

He traces the weapons back through the Activation Filter — the gate where every input is screened for survival meaning before his conscious mind gets access to it — and all the way down to the survival requirement the IC is defending.

It is the Pecking Order layer.

In a prehistoric world, rank within the group was not a nice-to-have. It was directly tied to survival: rank determined your access to food, protection, mates, and standing in the group. Lose enough rank and you lost your place. Lose your place and you were, very literally, at risk of dying. The IC was built to guard against that outcome with everything it had.

Today, a director walking past Nico's ideas in a meeting has no link to his survival. He is not at risk of exile. He is not losing resources. But the IC cannot tell the two apart — it received the same signal ("rank was just challenged") and it is running the same ancient response it has always run when rank is challenged: this is a survival emergency. Respond.

The IC's first move when rank is threatened is destroy the threat: fight back, assert dominance, make the challenger understand the cost of the disrespect. In a prehistoric setting, that move might have worked. In an office, in the middle of a meeting with a senior director, the social cost of firing that response is prohibitive. The IC may be ancient, but it is not entirely inflexible — it reads the room well enough to know destroy is not available here.

So it scans for the next exit.

And it finds one it has used before: food. The Physiological layer — the survival requirement governing basic bodily comfort — is a completely different part of the IC. But the IC discovered, sometime in Nico's past, that eating when the Pecking Order alarm is firing produces relief. Not resolution. Relief. The Anger quiets. The Stress drops a few degrees. The pressure behind his eyes eases. The IC felt that, and it learned: this works.

This is what the IC Solution calls Reward Confusion. The pain lives on the Pecking Order layer. The relief arrives from a completely different layer — Physiological pleasure. The IC cannot tell a real resolution from a fake one. It only reads the result: alarm was loud, then it was quieter. I should repeat the action that produced that. So it stamps eating-after-humiliation as a survival strategy — and now it fires the whole sequence every single time the Pecking Order alarm goes off.

The IC does not know the difference between fixing the problem and making the alarm go quiet. It only knows what worked last time.

That is the trap. The actual status problem — being overlooked, being uncredited, the slow erosion of being unseen at work — stays completely unaddressed. The IC just temporarily quieted its own alarm. And a temporarily quieted alarm always restarts. Louder.

And now the chain is complete, end to end.

The meeting sends a Pecking Order signal → the Activation Filter catches it before Nico does → the IC receives it as a survival emergency → it fires Anger, then Stress, then Cravings → the Cravings drive him to the kitchen → he eats → Physiological pleasure briefly quiets the Pecking Order alarm → the IC takes the reward. A complete, closed loop. That loop has a name: a hijacking. He was hijacked like this, quietly, for years.

And this is exactly why willpower never worked. Willpower is a conscious tool. It burns energy and it tires. The IC runs a subconscious program on almost no power and it never tires — it will outlast willpower every single time. And it fires first, underneath the conscious mind, before Nico ever gets a rational vote on what to do. He was not weak. He was using the wrong tool against the wrong system.

He is watching the chain from outside it now. He is not inside the craving. He is not the craving. And from outside it, he can see that the craving is a false signal on top of something real.

There is no food in the world that will fix what happened in that meeting. No amount of eating will raise his standing with that director. The IC found a shortcut between Pecking Order pain and Physiological relief and called it a solution — and it is not. It is the most comfortable form of the problem.

But the meeting is over. The director is not in the kitchen. The Pecking Order alarm is still firing even though the threat is gone. So what does Nico actually do now?

He has options. The craving does not have to command him. He can let it pass — notice it, name it, and not hand it the kitchen. He can also think about the real need underneath the alarm: he is being overlooked at work, and that is something worth addressing, not something worth eating around.

The craving is not the problem. It is the IC's solution to a different problem — one that food cannot touch.

He puts the craving down. Not by fighting it — by not obeying it. He is separated from it; it no longer has to run him. And in the space that opens up, the human drives come back online.

Intrigue — instead of pressure, curiosity. He got interested in the question: what is actually going on at work, and what could I actually do about it? That question had energy to it that the kitchen did not.

Appreciation — he noticed what was real and working: the colleagues who did see him, the project he was proud of, the clarity he had about his own skills. The IC had been running a distorted account. He could run a more accurate one.

Engagement — he put his full attention on the actual problem instead of the substitute one: being overlooked at work, and how to address it in a way that might actually change something. He wrote a few things down. Not all of it — just the next move.

Self-Improvement — he started getting better at something the IC had always short-circuited: sitting with the discomfort of being overlooked long enough to think clearly about it, instead of routing it through the kitchen.

Purpose — and underneath all of it, the larger thing: the kind of professional he wanted to be, and the kind of response he wanted to have when the moment tried to shrink him.

The craving still arrived. It did not disappear the first time, or the second. But each time he named it and watched it from outside — saw it as the IC running its Reward Confusion loop — it had a little less grip. Because a signal you can see clearly can no longer convince you that it is you.

Nico did not stop eating. He ate dinner. He ate lunch. He stopped going to the kitchen after being dismissed, because he stopped believing the craving was hunger. It was the IC trying to quiet a Pecking Order alarm through the only exit it had found. Once he could see that, the exit stopped looking like relief and started looking like what it was.

The move is always the same: separate from the signal, read what the IC is actually defending, and choose what the situation needs — not what the survival system demands. That is what the IC Solution teaches. Not for this one craving. For any pattern the IC has built around a survival need it does not know how to address.