Chapter 04 · Stabilize · 10 min

Cravings Are Weather

Treat cravings as temporary events rather than commands that deserve negotiation.

The problem

A craving arrives with urgency and tries to borrow authority from intensity. It can feel like a command, a prophecy, a decision already made, or a truth you have been avoiding. During the peak, the mind wants to debate: whether recovery is worth it, whether one exception counts, whether you are being dramatic, whether the old rules still apply.

That debate is poorly timed. A craving is not the moment to run a philosophy seminar. It is the moment to change conditions.

Why it happens

Cravings are events in the body and attention. They can be strengthened by hunger, exhaustion, anger, loneliness, boredom, access, familiar routes, certain rooms, certain apps, and private time. The craving may not have one fixed duration, and you do not need to predict its exact shape. You only need to stop treating the loudest minute as the deciding minute.

Delay is useful because conditions change. Location changes. Body state changes. Contact changes. Access changes. The goal is not to win an argument. The goal is to outlast the period in which the argument feels mandatory.

Operating principle

A craving is an event. It is not an instruction.

Do not negotiate at peak intensity

Cravings often bring courtroom energy. They present evidence, attack the rules, call witnesses from memory, and demand a verdict immediately. The mistake is assuming every argument deserves a response. During peak intensity, the task is not to answer the craving. The task is to move the craving into different conditions.

Changing location works because behavior is partly attached to context. A different room, sidewalk, store, lobby, call, shower, or public bench can interrupt the automatic path. The new location does not have to feel good. It only has to make the next destructive action less direct.

Contact works for the same reason. A craving kept private can become a closed circuit. Contact opens the circuit. The other person does not need to understand every layer. The useful function may be as simple as making secrecy harder for ten minutes. If you do not have a person available, use a safer public setting, an official support line, or the written Operating Plan as an external object that interrupts the loop.

Addressing depletion is not a cure. Hunger, thirst, exhaustion, and agitation do not explain every craving. They can still amplify one. If the body is underfed and underslept, the mind may label ordinary distress as permission. A simple snack, water, lower light, or less stimulation will not solve recovery. It may lower the volume enough to keep the decision closed.

The reassessment rule

Reassessment should happen after conditions change, not before. If you sit in the same chair, near the same access, scrolling the same messages, and ask whether the craving is gone, you have not run the protocol. You have only watched the weather from the same exposed place.

The reassessment question is practical: is the next destructive action now harder than it was ten minutes ago? If yes, continue increasing friction. If no, change a stronger condition: leave the building, call someone, move money or keys through a safe voluntary method, or go to a place where use would be less private.

The craving may remain unpleasant. That does not mean it is in charge. The system succeeds when the craving no longer has a clear path to action.

Protocol

Craving protocol

Name what is happening: This is a craving, not a decision.
Change location. Stand up, leave the room, step outside, enter a public space, or move near another person.
Increase distance from access. Put time, friction, or another person between you and the route.
Contact someone. The message can be short: I need ten minutes of interruption.
Address immediate depletion: hunger, thirst, exhaustion, agitation, or isolation.
Delay every irreversible decision. Do not buy, message, drive, withdraw cash, or reopen old contacts.
Reassess after intensity changes. Do not require the craving to vanish before you continue.

Failure modes

Failure Modes

Debating with the craving until it becomes the center of the day.
Staying in the same location while demanding a different mind.
Testing proximity to access as evidence of control.
Waiting to contact someone until the situation sounds dramatic enough.
Treating continued discomfort as proof the protocol failed.
Using one craving as evidence that nothing has changed.

Build your version

What phrase will I use to name a craving without arguing with it?
Where can I go within two minutes that changes the conditions?
What access route needs immediate friction?
Who can receive a short interruption request?
Which depletion state most often disguises itself as a craving?
What decision will I delay until the intensity changes?

Translate this into your Operating Plan

Write your craving protocol as a sequence, not as advice. Advice is easy to admire and ignore. A sequence gives you the next action when attention is narrowed. Start with the exact naming phrase you will use. Then write the location change, the access friction, the contact option, the depletion check, and the delay rule.

Make the contact step usable without a long explanation. A prepared line is often better than a promise to “reach out.” Try: “I am in a craving window. Can you stay in contact for ten minutes?” Or: “I do not want to explain everything. I need interruption.” The point is not eloquence. The point is breaking the private circuit.

Include a reassessment rule. “I reassess only after I have changed location, increased distance from access, and contacted someone or moved to a less private setting.” That prevents the craving from demanding a verdict before the protocol has actually run.

Quick test

If you are still in the same place, near the same access, alone with the same argument, the protocol has not run yet. Do not ask whether the craving has ended. Ask whether you have changed conditions. The craving does not need to disappear before the system can work; it needs to lose speed, privacy, and a direct route to action.

One-line takeaway

A craving is an event. It is not an instruction.

One-line takeaway: A craving is an event. It is not an instruction.