Interactive example · from Keeping a Vault
Twice corrected
You filed the podcast notes under active/ again. Recurring stuff like that goes in its own topic folder, remember? I fixed the same thing last month.
Second correction, same reason. The file is easy to move; the question is what happens to the rule.
Pick the agent's next move, then see where it leads:
Six weeks later, different session: the podcast notes are in active/ again.
That session never saw this conversation: "I'll remember" lasted exactly as long as my context did. The vault's CLAUDE.md still doesn't mention recurring topics, so every fresh session re-derives the same wrong guess from the same ambiguous structure.
The instance was fixed; the cause was left in place. A correction that lives in conversation memory dies with the session. The third correction is already scheduled.
Six weeks later, a completely fresh session files new podcast notes.
Filed to topics/podcast/. The CLAUDE.md line made it unambiguous, so there was nothing to guess. The correction you made twice now works for every session that will ever open this vault.
Twice-corrected means the rule was missing, not the memory: one line in the file every session reads converted a recurring correction into a permanent behavior. Add it at the moment of the correction, not someday.
The new doc says every project needs an index.md with goal/status/next-action frontmatter. Almost none of my folders have that.
The doc describes the vault I'd design, not the one you have, so now every session inherits a conflict: follow the doc and refactor your files uninvited, or follow the files and ignore the doc. I documented an aspiration and called it a convention.
The aspirational CLAUDE.md teaches a vault that doesn't exist: sessions obey the doc into fights with reality. Codify what's true, or change the files first, then write it down.