RESET
THE
MACHINE
A 30-Day Field Manual for Taking Back Control of Any Behaviour
This is not a journal. This is not a feelings workbook.
This is a diagnostic tool. Because the behaviour does not run on the story. It runs on state.
YOU HAVE TRIED THE WORKBOOKS.
You rated your mood. Identified your triggers. Journalled through it. And then the behaviour ran anyway. Because every programme, every framework, every well-meaning tool worked on the story. The behaviour does not run on the story.
Story Solutions
Feelings workbooks sell because they make you feel like you’re working on it. There is a difference between working on a problem and feeling like you’re working on it. A profitable one.
The 100ms Hijack
The behaviour fires 100 milliseconds before your prefrontal cortex registers what is happening. By the time you reach for the journal prompt, the loop has already completed.
State Not Story
The loop runs on nervous system load. On the machine screaming for a rapid state change. No amount of narrative reframing addresses a physiological demand.
Dependency By Design
Data tools make you independent. Independent people do not keep buying the next programme. The industry is not incentivised to fix the problem permanently.
The machine is not broken. It is installed. The installation is not a flaw in your character. It is the output of a specific environment meeting a specific machine at a specific point in development.
– Reset The Machine, Day One Mechanic’s NoteTEN MINUTES.
THIRTY DAYS.
YOUR MACHINE MAPPED.
Morning Protocol
- Morning Tone: circle the number that fits right now
- What state did the machine wake in. Factual. No editorialising.
- Primary load right now: what is the machine actually managing
- Error codes live today: anxiety, anger, numbness, craving
- One thing that could close the Gate before it arrives
Evening SITREP
- Day’s Tone average: what did the machine actually produce
- Error codes that fired and at what point in the day
- Observer protocol: was it available when needed
- Servicing today: honest account, not the aspirational version
- One specific implementable thing that changes tomorrow. Not a resolution. One thing.
Establish The Baseline
You do not change anything. You see clearly for the first time without the PR Firm editing the account. Seven days of data is enough to see the machine’s baseline.
Apply The Diagnostic
You begin connecting the current activation to the original installation. The machine stops being a mystery and starts being a map.
Stay In The Cockpit
Complacency is the specific threat at this stage. The data tells you when the drift begins before it becomes a slip.
Build The Architecture
The non-negotiables. The early warning signals. The post-programme protocol that does not collapse when the thirty days end.
7 SIGNS THIS IS YOUR WRENCH
- 1You have tried journalling and the behaviour ran anyway
- 2You know something is wrong with how you are coping but cannot name the specific architecture of it
- 3You have put the drink down or cut back and the evenings are still difficult and you do not know why
- 4Bob is loud. The PR Firm is convincing. And you are exhausted by both.
- 5You have been to therapy, done the steps, read the books, and still feel like you are managing rather than operating
- 6You want data about your own machine, not someone else’s framework imposed on top of it
- 7You are done with story solutions. You want the wrench.
Works on any behaviour that runs on state. Drinking, eating, scrolling, rage, withdrawal, gambling, numbing of any variety. Same architecture. Same tool. No labels required.
FAQ
No. Reset The Machine stands completely alone. Under Load gives you the framework: the wiring, the installation, the error codes. This manual gives you the tool. You need a behaviour that is running you. That is the only entry requirement.
No. Same architecture, same tool, any behaviour that runs on state. Drinking, eating, scrolling, rage, withdrawal, gambling, numbing of any variety. The machine does not care which loop is running. The diagnostic works the same way.
A habit tracker logs what you did. This logs what the machine produced and what conditions produced it. One is a record. The other is a diagnostic. Records tell you what happened. Diagnostics tell you why.
Ten minutes total. Five in the morning before the day starts. Five in the evening before you sleep. The gap between them is the work. The ten minutes is just the logging.
Because week two of this is built specifically around the complacency that kills every other programme at that stage. The data from your own first week drives week two. It is not a generic programme. It is your machine’s specific architecture being read back to you.
This is a working document. You write in it daily. The paperback is the primary tool, available now on Amazon. The ebook is available direct if you want to start today or prefer to print your own pages.
THE MACHINE IS NOT BROKEN.
IT IS INSTALLED.
After 45 years and over a year without the drink, here is what I know with absolute certainty. You do not have a character flaw. You have a machine that has never been properly serviced. This is the wrench.
Both formats available now