Method · Differentiator · Forward-thinking
Golden Record
Canonical memory, separated from working notes
A method for separating canonical memory from working notes, experiments, and archived loops so a system can stay useful over time.
What the Golden Record is
A canonical layer for what should stay true when everything else changes. Decisions, definitions, load-bearing relationships, irreversible commitments. The things that survive a context reset.
What it isn't
Not every note deserves to become canon. Most don't. A working note becomes canon when it stops being a question and starts being a rule.
Canonical, working, experimental, archived
Working notes are for motion. Experimental loops are for bets. Archive is for history. Canon is for decisions that should survive resets. Four shelves, four jobs; mixing them up is what breaks systems.
How it helps AI tools stay grounded
Pruning is not deletion. Pruning is governance. A system that remembers everything equally eventually remembers nothing well, and an AI assistant pulling from that system answers as confidently as the noise allows it to.
How I'd adapt it for a team
Start with one canonical file per domain and one explicit archive policy. Add the rule that canon changes only through a named ceremony, with a date and a reason. Everything else stays out of canon by default.
