Every knowledge base dies the same way: notes pile up, two of them disagree, links point one way, the index describes notes that have since changed. Nobody notices, because nobody reads the whole thing, and the tool that is supposed to apply the notes starts applying the wrong ones.
The failure is not laziness. It is that upkeep was never made mechanical. Here is how the vault keeps itself honest.
An audit that runs on every change
A small script checks three things and fails the build if any is wrong:
- every link between notes is returned by a link back
- every note listed in the index exists, and every note that exists is listed
- no index line is thin, meaning shorter than a hook a stranger could search by
It runs automatically whenever the repository changes. The first time it ran for real it found a class of problem I had not thought about: links that went one way. A note referred to another, but the other did not refer back, so the relationship was invisible from one side. A dozen of those, fixed in an hour, and now impossible to reintroduce.
A gardening pass, on a schedule
Monthly, or after a burst of saving, a longer pass with a human in it. It merges near-duplicates. It pulls a general idea out of a project note into its own note. It rewrites index hooks that say what a note is called rather than what problem it solves.
The first full pass extracted one pattern from four different project notes that had each half-described it. Four teams had learned the same lesson about working around a tool’s limits, in four places, and none could find the others.
The conflict rule
This is the one that matters most, and the one most knowledge bases lack.
Before saving, search for notes on the same topic looking specifically for contradiction, not just relevance. If the new lesson contradicts a saved one, stop. Did we change our minds, or is the new information wrong? Never guess, and never save both.
On a change of mind, the old note is updated in place with a dated line: “Superseded on this date: previously said X; now Y because Z.” Git keeps the full old version. The note a reader or a tool finds is always the current view, with its history visible.
On recall, the same rule runs in reverse. If the tool surfaces two notes that disagree, it flags the contradiction instead of silently picking one.
This is what makes the loop continually improving rather than continually growing. A vault with the conflict rule gets more right over time. One without it gets bigger.
Why this is a leadership question
For a team, the audit script is a few hours of work and the gardening pass is a recurring hour on someone’s calendar. What makes it happen is the same thing that makes a backlog get groomed: someone owns it, and it is treated as part of the work rather than a nice-to-have.
A company that asks “how do we make sure what we learn about AI gets kept” is asking for this. The notes are the easy half. The gardening is the half that decides whether they are still true in a year.