A Self Destructive Behaviour Workbook That Works on State
£14.97
A self-destructive behaviour workbook, unlike anything in the recovery space. This is the thirty-day operational tool that shows you what the machine is actually producing, in actual conditions, day by day, until the pattern is undeniable and the next move is obvious.
Not a journal. Not a programme. A diagnostic log.
£14.97 — Digital PDF
Description
A Self Destructive Behaviour Workbook That Works on State, Not the Story
You already know what you keep doing. That is not the problem.
You have done the understanding. You can explain the pattern. You have read the books, possibly done the therapy, possibly done the programme. You know where it comes from. You can describe the trigger. You have produced the insight more times than you can count.
And you have done the thing again anyway.
That gap, between knowing and stopping, between the insight and the behaviour, is not a character problem. It is a state problem. And you cannot think your way out of a state problem.
Reset The Machine is the thirty-day field manual that works on the state. Not the story. The state.
What It Is
209 pages. Thirty consecutive days of structured daily logging. Morning to evening.
Every day, you produce a factual operational report on one machine: yours. What state it woke in. What load it is carrying right now. Which error codes are live and at what intensity. What servicing happened and what did not. What one specific implementable thing changes tomorrow.
No narrative. No reflection prompts designed to guide you toward a particular emotional destination. No programme language, no labels, no identity frameworks built around what you are stopping or starting.
You are an operator running diagnostics on a machine. The data belongs to you. What you do with it is your operational decision.
What Error Codes Means
The manual works with four error codes: anxiety, anger, numbness, craving.
The behaviour the error code produces, whether that is alcohol, food, spending, screens, work, substances, gambling, or anything else the machine has adopted as a regulation strategy, is not what the log tracks. The log tracks the code underneath it. Because the code is where the loop actually lives. The behaviour is just the output the machine defaults to when the code fires and no other intervention is in place.
This is the framework that makes the manual work regardless of what the machine is running.
The Four-Week Structure
Week One: Establish the Baseline
Week One does not ask you to change anything. It asks you to see clearly. The morning protocol, the Tone check, the error code tracking, and the evening SITREP are diagnostic instruments this week. You are calibrating the measurement tool before you use it. Do not assess Week One while you are in it. Log it. Complete it. The assessment comes later, when you have enough data to see a pattern rather than a single day.
Week Two: Apply the Diagnostic
You have seven days of data. Week Two applies it. The questions become more specific. One protocol change, identified from your own Week One evidence, goes into operation on Day Eight. The focus this week is the relationship between the current load and the specific error code patterns the first week revealed.
Week Three: Operate More Precisely
Week Three moves from reading the machine to operating it. The machine is now well enough known that the diagnostic can go further than it could in the first two weeks. The focus is sovereignty in daily conditions: what the operator’s position looks like in the actual relationships, actual work, actual triggers, and actual decisions of the ordinary day.
Week Four: Build What Carries Forward
The final week. The focus is consolidation and the construction of the post-programme maintenance architecture. The specific ongoing practices that carry what has been built beyond Day Thirty. The programme ends on Day Thirty. The practice does not. Week Four is where that transition is designed rather than left to chance.
What Every Day Contains
Each day runs the same structure, morning and evening, two to five minutes each session.
Morning Wake time. Morning Tone on a 1 to 10 scale. A brief factual account of the state the machine woke in. Four protocol checkboxes. One pre-named threat before it arrives.
Load Diagnostic The specific current load. Which error codes are live. Intensity. What triggered them or is likely to today.
Evening SITREP Day’s Tone average. Error codes that fired and when. Observer availability. Honest servicing account. One specific implementable change for tomorrow. Not a resolution. One thing.
Mechanic’s Note Every day carries a short operational briefing specific to that day’s position in the programme. Direct. Mechanistic. No recovery language.
The Weekly SITREPs
At the end of each week, a structured review pulls the data together. Tone averages. Week on week direction. Error code patterns. What the protocol change produced. What the next iteration looks like. These are not reflection exercises. They are the first point at which data becomes pattern, and pattern becomes something you can act on.
The Forensic Audit
Day Thirty closes with a full programme debrief. The complete Tone record across all thirty days. The definitive account of this machine’s primary and secondary error codes, confirmed by data. The PR Firm’s most convincing brief, named on the record. The post-programme architecture, confirmed and carried forward.
Read back through every entry before completing it. Not quickly. The machine that has spent thirty days producing honest daily entries deserves a complete and careful read of its own output.
The Book Behind It
Reset The Machine was built as the operational companion to Under Load: Why human beings keep doing the things that are destroying them, and how to take back the controls.
Under Load explains the architecture: why the machine runs the loop it runs, what the error codes are, what the PR Firm does, what the Gate is, and what sovereign operation actually looks like. The manual puts that framework to work in daily conditions over thirty days.
You do not need to have read Under Load to use this manual. But if you have it, read it first. The manual will mean more when you understand what it is asking you to do and why.
Under Load is available in the shop.
Format and Price
Digital PDF download. 209 pages. Formatted for print if you want to work with it on paper.
£14.97
A physical paperback edition is coming. If you buy the PDF now, you have the working tool today.
Pick up the wrench.
[Add to Cart — £14.97]
Reviews
There are no reviews yet.