// Externalize your memory · lesson 03
What actually goes in the memory
Deciding to externalize your memory is step one. Step two is knowing what to actually put in it, and this is where most people quietly fail. They either save nothing, so the files stay empty, or they save everything, dumping raw transcripts until the memory is a landfill nobody can retrieve from. A memory only earns its keep if it is curated, and curation means choosing what is worth keeping.
The things worth keeping have a common trait: they are expensive to reconstruct and not derivable from what you already have. Decisions and the reasoning behind them, because the decision is easy to see later but the why is gone if you do not capture it. Context that is not written anywhere else, the constraints, the goals, the things that are true about the project but live only in your head. What failed and why, because a recorded dead end saves you from walking down it again. The current state of the work, so a fresh session can pick up without an archaeology dig.
What should you deliberately leave out?
Anything you can regenerate or look up. Do not save what the code already says, because the code is the source of truth for how the code works and a stale note about it is worse than no note. Do not save raw conversation transcripts, they are all signal-to-noise ratio and no structure. Do not save the obvious, the things any competent read of the project would surface on its own. The test is simple: if this would be easy to reconstruct from the artifacts that already exist, it does not belong in memory. Memory is for the things that would be lost, not the things that are already written down somewhere durable.
The reason to be this strict is that memory has a cost, and the cost is retrieval. Every low-value entry you save is noise the high-value entries have to be found through later. A memory of five hundred junk notes and ten crucial ones is often worse than a memory of just the ten, because the ten are now buried. Curating is not tidiness for its own sake, it is protecting the signal you will need to find under pressure. Hoard everything and you have technically saved it all and practically saved nothing, because you cannot find the piece that matters when the moment comes.
The takeaway: Save decisions, hidden context, and what failed, the things expensive to reconstruct. Leave out anything the code or existing artifacts already record, because hoarding buries the signal and a memory you can't retrieve from is no memory at all.