Documentation as a Practice
The single most powerful instrument available to a person inside the dynamic costs nothing. What to record, how, and why it changes everything before it is ever shown to anyone.
Most of what this newsletter offers is a way of reading. This piece is different: it is a practice. Something done, regularly, with your hands. And it earns that treatment because documentation sits underneath everything else the framework describes: the pattern recognition, the boundary work, the exit itself. It is the instrument that converts experience into evidence, and inside a dynamic built on the disputing of your experience, that conversion is not administrative. It is structural.
Why the Record Beats the Memory
Start with the problem documentation solves, because the practice only makes sense against the problem.
The dynamic this newsletter describes runs, in large part, on the instability of your account. Gaslighting is not a series of lies; it is a sustained campaign against the reliability of your memory. That never happened. That’s not what I said. You’re remembering it wrong. You always twist things. Each individual dispute is small. The cumulative effect is not: after enough disputes, you stop trusting the only witness you have and once that trust is gone, the operation’s version wins by default, not because it is more accurate but because yours has been destabilised into silence.
Now notice what this campaign requires to work: it requires your account to live in memory, because memory is disputable. Memory fades, blends, and bends under confident contradiction: this is ordinary human cognition, not weakness, and the operation exploits it as a design feature. A contemporaneous written record is a different kind of object. It does not fade. It does not update when someone insists. It says what it said on the date it said it. You cannot be argued out of a page.
This is the first and most important function of documentation, and it has nothing to do with courts or audiences: the record is for you. It exists so that when the campaign against your memory arrives there is somewhere outside your head where reality is stored.
What to Record
The practice is simple, and its simplicity is what makes it sustainable. After an incident (an argument, a broken agreement, a silence, a rage, anything that will later be disputed or fogged) write down:
Date and time. This is what turns anecdotes into a pattern. Ten undated memories are a mood; ten dated entries are a record, and the dates are what later reveal frequency, clustering, and escalation.
What was said and done, factually. As close to verbatim as you can manage, in plain description. He said X. I said Y. She then left and did not speak to me for three days. Write it the way a camera would testify, not the way a wound would. This is not because your feelings are inadmissible, it is because the factual layer is the part that cannot be argued with later, by them or by your own doubting mind.
Context. What preceded it. What the stated reason was. Who else was present, if anyone.
Your state, separately. One or two lines: I felt sick for the rest of the evening; I could not concentrate at work the next day. Kept separate from the factual layer, this becomes its own pattern over time: the record of what proximity to the dynamic actually costs you, which is easy to minimise day by day and impossible to minimise across sixty dated entries.
That is the whole entry. Four elements, five minutes, written the same day while the detail is intact. Not an essay. Not a journal of feelings: a log of events. The discipline of brevity is protective: a practice that takes five minutes survives; one that takes an hour becomes another burden the dynamic is imposing on you.
How to Keep It Safe
A record only works if it exists when needed and stays out of the operation’s reach. Three rules cover most situations.
Keep it somewhere with independent access: an email account only you know exists, notes stored under an innocuous name in a location the other person does not reach, or physical pages kept outside the shared space entirely. Assume, as a planning posture, that anything on a shared device or a known account is readable. Never announce that the record exists; a known record becomes a target for deletion, for ridicule, for pre-emptive counter-narrative and announcing it converts a quiet instrument into a live battlefield. And back it up once, somewhere second, so its survival does not depend on one device.
If your situation involves genuine danger, documentation belongs inside a broader safety plan made with people qualified to help build one: the record supports an exit; it must never be allowed to provoke what it was meant to protect against.
What the Record Becomes
Kept for a few months, the log begins returning value in four distinct ways, in ascending order of visibility.
It stabilises you. This is the quiet one and the most important. The next time reality is confidently rewritten in front of you, something is different: you may still feel the fog arrive, but you now know the fog is a move, because the page at home says what happened. You do not even need to open it in the moment. Knowing it exists changes your relationship to the dispute: you stop litigating your own memory in real time, because the litigation has already been settled in writing.
It reveals the pattern. Individual incidents are deniable; that is why the dynamic happens in incidents. Sixty dated entries are not deniable, least of all to you. Reading a quarter’s log does something no single memory can: it shows frequency, it shows triggers and it shows the cycle running on schedule. The vague sense that “things keep happening” becomes a documented structure with a shape. This is where documentation and pattern recognition, covered elsewhere, become the same practice: the log is pattern recognition given a body.
It converts your account into an account that can be shared. If and when you choose to tell someone (a therapist, a lawyer, an HR process, a family member) you arrive not with a distressed narrative competing against a calm denial, but with dates. The asymmetry this newsletter has described elsewhere, where their composed version outranks your emotional one, is precisely the asymmetry a contemporaneous record reverses.
It serves the exit. Custody, employment disputes, tenancy, protective orders: in any formal process, contemporaneous records carry a weight that recollection does not. This is the function people usually start documentation for, and it matters. But notice that it is the last function, not the first. The record’s legal life is occasional; its daily life is the first three.
One reframe, because the practice sometimes meets an internal objection: keeping a file on someone I love feels like a betrayal of the relationship. Read that objection structurally. A relationship that is not running an operation is never threatened by a diary: millions of people keep one, about everything, forever, harmlessly. The only dynamic endangered by an accurate record of events is a dynamic that requires events to stay disputable. The discomfort is real, but it is not evidence against the practice. It is the trained reflex of a system that has always preferred your account unstable, objecting, through you, to the stabiliser.
Documentation is the quietest instrument in the framework. It confronts no one, announces nothing, changes nothing visible. It simply ends the era in which your reality was a matter of debate.
Once you can read the code, the code stops working, and the record is where the reading is kept.