Using another memory tool alongside Otto (and why brain/ has to stay the only one)

Short answer: another memory tool will not damage your booking folder, but it will quietly start telling you things that are out of date. Keep brain/ as the only place anything is written, and treat any other memory tool as read-only over it.

What a separate memory tool actually does to your files

We tested this on a throwaway booking folder: built a folder with a profile, House Rules, a client page and a stage folder, recorded a fingerprint of every file, filed one of those client facts into a separate memory tool, then re-checked every file.

Nothing in the booking folder changed. Not one byte, no file added, no file moved, no file removed. The content had been copied into that tool's own database, which lives somewhere else on your computer entirely. So if you ran one of these and then worried it had rearranged your Booked Solid files, it did not. It only read them.

The real problem: two memories that drift apart

Here is what went wrong in the same test, and it is worth understanding because it is the failure you will actually hit.

After filing the client fact, we corrected the truth in the booking folder: the client had moved from a yearly gala to a spring luncheon, and their floor went from $1,500 to $4,000. We changed the client page and the House Rules, the way you would after a real phone call.

Then we asked the separate memory tool about that client. It answered "yearly gala, $1,500", confidently, with no hint that it was stale. It had no idea the file had changed, because nothing tells it.

That is the whole risk in one sentence: your second memory does not know when your first memory changes. Otto reads the current file and says $4,000. The other tool says $1,500. Both sound certain. One of them quotes your client the wrong number.

The rule

• Everything you want remembered goes in brain/ inside your booking folder. Otto indexes it, writes to it, and reads the live version every time.
• Any other memory tool is read-only over that folder. Let it look. Do not let it become the place a fact is stored.
• Never keep the same fact in two places. The moment a client detail lives in two memories, one of them is wrong and you cannot tell which from the answer alone.

Newer versions of the app write this rule into your booking folder's own CLAUDE.md, so a terminal session reads it too and will not be talked into starting a second store.

Being straight about memory in general

AI memory is not solved, ours included. It sometimes has to be told to go and look at what it already knows. If Otto answers as though it has forgotten something you know is filed, say "check your brain first" and it will usually find it. That is a real limitation today, not a thing we are hiding.

Common ways people ask this

• Will a memory palace tool break my BookingHQ folder?
• Did that memory tool move my Booked Solid files?
• Can I use a second memory system with Otto?
• Why does the terminal remember something different from the app?
• Where does Booked Solid keep what it remembers?

If you already ran one and want a second pair of eyes on your folder, open a ticket at support.booked.kivimedia.co.