I keep coming back to one sentence I wrote in early July, because almost everything we have built since turns out to be that sentence, enforced.
The sentence is short: anything that does not live in the Brain, our record of spec and strategy and decisions, or on a system that is actually running, repos and remote-operated infrastructure, is leakage. Not a filing error. Leakage: inefficiency and lost knowledge, the same way a pipe with a hole in it loses water whether or not anyone notices the puddle. There are exactly two honest homes for anything we know. A head, a chat thread, a local file that lives on one laptop, an un-consolidated dashboard only one person checks: none of those are homes. They are places knowledge goes to disappear slowly, in a way that feels like progress right up until someone else needs what you knew and cannot find it.
I wrote it because I kept catching the same category error in slightly different clothes. Something a tool had already learned how to do, its own playbook, its own operating knowledge, would get treated as company operations to be filed away in the wrong place, when a tool that lives in our own record should carry its own playbook there, in its home, not scattered into whatever folder happened to be open when someone wrote it down. Naming the rule once, plainly, stopped me having to re-litigate the same misfiling every time it showed up in a new shape.
There is a corollary I care about as much as the rule itself: a static record that could instead be operated should migrate toward being operated. A live inventory belongs in a system that can act on it, not a document someone has to remember to reread. A secret belongs in a secret store, not a note, however well organised the note is. The test is not "is this written down somewhere." Almost everything eventually gets written down somewhere. The test is whether it has exactly one home, and whether that home is the kind of place that keeps it alive rather than the kind that quietly buries it.
A few days before I wrote that rule down, I had already generalised a narrower version of it: nothing in our working record should ever depend on a link pointing somewhere else that might not be there tomorrow. If a piece of knowledge needs context from elsewhere, state the fact plainly where it's needed rather than pointing at it and hoping the pointer holds. That was the same instinct, applied to a smaller problem first: knowledge that depends on something outside itself to be understood is knowledge halfway to leaking.
I did not know, writing this down, that a month later we would measure exactly how much this mattered. An audit found that the overwhelming majority of one night's working sessions had produced findings that lived nowhere anyone else could find them, each one perfectly recorded in a private scratchpad and invisible to everyone else the moment that session ended. That is the rule I am describing here, violated at scale, discovered by counting. The fix that followed was not a reminder to be tidier. It was building the audit itself into a standing check, because a rule nobody verifies is a hope, not a rule.
Everything else in how this estate holds what it knows, the logging discipline, the audits, the habit of routing a lesson to the place that can act on it rather than the chat where it happened to surface, is downstream of this one sentence. Two homes. Everything else is leakage. It is the plainest rule I have ever written, and it is the one the rest of the discipline stands on.