Fighting Drift

I keep one document about my studio, and its single rule is that it may not contain the past. When something is finished, the line describing it is deleted, not marked done. When a plan changes, the old plan is overwritten, not struck through. The document holds the present and nothing else. It took me a while to understand why it had to be written that way, and the reason turned out to be the most useful thing I learned this year about running anything small.

Every document drifts

Every document starts drifting from reality the moment you write it. A plan is accurate on the afternoon you write it and a little wrong by the next morning, because the thing it describes kept moving and the description did not. A dashboard shows you a number that was true when the query ran. A README describes a system as it stood when someone last remembered to update it. None of these are lies when written; they become lies by sitting still while their subject does not. The gap has a cost that is easy to miss because it accrues in silence: you make a decision against the map, the map has drifted from the territory, and you find out only when the decision lands wrong.

You can't out-discipline it

The naive fix is discipline — keep the documents updated. I tried that for a while. It fails, and not for lack of discipline: the number of representations multiplies faster than any one person can maintain, and the moment you are maintaining maps for a living you have stopped doing the thing the maps were meant to describe. The maps begin to eat the territory.

Keep only what regenerates

What works is the opposite move. Keep as few representations as you can, and make the few you keep regenerable from the one thing that cannot drift — because it is not a description of the work but the work itself. For a studio that thing is its version history: the literal, timestamped record of every change actually made. Everything else I generate on demand and throw away. I do not store a report on the state of a project; I recompute it from the history when I need it, which guarantees it is current, because it is read from the territory at the moment I ask. The present-only document is the same instinct applied to intent. A version history cannot tell you what you are trying to do next — so that, and only that, gets written by hand, and rewritten rather than appended, so it can't quietly become the past pretending to be the present.

When the reader is a machine

This stopped being optional the moment I began running the studio with an agent instead of by hand. A person carries a fuzzy, constantly-updated sense of what is actually true and silently discounts the stale documents; you read the architecture note and think, half-consciously, that's three weeks old, the auth part changed. An agent does no such thing. It believes what it reads. Hand it a drifted document and it will act on the drift with total confidence and considerable speed. The only safe thing to hand it is the territory — the history, the live state — and let it derive the rest. Working with the model forced a rigor about truth that I should have had on my own and didn't: a representation either regenerates from something real, or it is a liability waiting to mislead whoever trusts it next — and increasingly, whoever trusts it next is not a person.

There is a strand of philosophy that has been saying a version of this for a century. Reality, it argues, is not a set of static things to be catalogued but a process that is only ever occurring — so any fixed representation is already a snapshot of something that has since moved on. I used to read that as a metaphysical claim and find it faintly airy. Running a studio turned it into an operational one. The work is real; the documents about the work are snapshots; snapshots drift. So you keep them few, you compute them fresh when you need them, and the single thing you write by hand is the one thing the record cannot hold for you — where you are trying to go, in the present tense, with the past deleted behind you. Fighting drift turns out not to be a chore at the edge of the real work. It is most of what running the thing is.