Stop your AI from forgetting everything

A second brain, a project folder, a set of custom instructions, whatever you call your AI setup, it fails for one reason: the answers stop being true. There is no correct way to organize it. There is only whether it can find the thing, and whether what it finds is right.

The four ways it breaks

When your AI tells you something wrong, it is always one of these four. Naming the right one matters because each has a different fix.

1. Poisoning

A false fact sitting inside otherwise good information. It is not lying, it found something and used it as data, and the data was wrong. This is the easiest one to fix: ask it to double-check anything it is not sure about, or tell it to say so instead of guessing.

2. Bloat

Too much loaded at once. It has to scan everything to decide what matters, and when there is too much, the wrong things bleed into the answer. This is the one that creeps up as your files pile up, and it is the hardest to fix after the fact.

3. Confusion

A missing fact instead of a wrong one. It fills the gap with its own guess. This is the classic hallucination, and it is the quiet cousin of poisoning: poisoning means it grabbed something wrong and said it confidently, confusion means nothing was there and it answered anyway.

4. Clash

Two sources that disagree, usually because one is old. Your prices changed in June but the March version is still sitting in a file somewhere. When a question comes in, it has no way to know which one to trust, so it picks one, or worse, invents a third answer that splits the difference.

The fix for bloat: two kinds of information

Split what you tell it into two piles. Expertise is the rulebook: who you are, what your business does, your prices, your standing rules. Load that every single time. Situational is a specific customer, a specific week, a specific one-off. Pull that in only when you need it. Leaving situational details loaded permanently is exactly how bloat, confusion, and clash get made.

That last part matters. The audit should only report. Never let it fix, rename, or delete on the same pass that finds the problem. Read the list first, then decide.

The test that tells you if it is working

Think of something you saved. Try to find it yourself, without searching, just by walking through your own folders. If you can find it, your AI probably can too. If you cannot, neither can it. That is the whole test.

When you are ready to rebuild instead of patch

This guide names what went wrong. The next question is what shape to put it all back into so it stops going wrong. Small notes, one subject each, one short list on top, and the move almost nobody makes, which is checking that list before you write anything new down. Read the junk drawer guide.

← Back to the library