One Memory. Fifty Five Models.

I run fifty five models from one screen. Local ones on the machine under my desk. Claude. The big open weight models that live on someone else's hardware. A few from providers in China that I keep for experiments and nothing else. For most of this year every one of them started every conversation as a stranger. I would explain the business again. I would paste the same context again. Then I would close the window and whatever we had figured out was gone.

Meanwhile everything I actually know lives in one place. A vault of a few hundred plain text notes. The operating manual for my life, the runbooks, the build logs, the notes on what broke and why. The models could not see it. The notes could not see the models. Two halves of one brain, and the hallway between them was me, retyping.

Last week I closed the hallway. Every model now reads from the vault, and every conversation worth keeping flows back into it overnight. The build took a day. The hard part was not the plumbing. The hard part was a question I had never had to answer before: which of these fifty five should be allowed to remember what.

Two shelves, not one

The obvious build is one shared memory and let everyone drink from it. I got about an hour into that before I stopped.

Some of what is in the vault is a golf handicap and a store's ad spend. Some of it is my day job, where I work with people's estate plans. Some of it is a note about what my own weaknesses are and how my assistant should handle me on a bad day. Those are not the same kind of secret, and the models are not the same kind of reader.

So there are two shelves now. The ops shelf holds the ventures, the builds, the hobbies, the things I would say out loud at a dinner. All fifty five models can reach it. The private shelf holds the day job, the profile, the systems that run the house, and the manual itself. That shelf is reachable by exactly three kinds of reader. The models that run on my own machine. Claude, which I have decided to trust with it. And the small agents I wrote myself, which are really just those first two wearing a name tag.

The rule for the private shelf is short. If I would not read it to a room, it does not go on a shelf a stranger can reach.

The night shift

Memory that only goes one direction is a library. I wanted a diary.

So at twenty past eleven every night, a job wakes up, collects the day's conversations, and writes a one paragraph summary of each. The summary is written by a small local model, an eight billion parameter thing that runs on my machine, so the act of summarizing a private conversation never leaves the house. Then the summaries and any changed notes are pushed to both shelves and reattached to every model that should see them. By the time I sit down in the morning, whatever I worked through with any of them the day before is part of what all of them know.

The first night it digested four chats. That is not a lot. It is the right four, which is the part that took the day.

Where it nearly went wrong

Three things, and I am writing them down because I will forget them and you might need them.

The first was a word. My guard against exporting day job conversations looked for a folder called Red Cross. The folder is called 1 Red Cross, with a number in front, because I sort my folders that way. The guard never matched. For a stretch this summer, conversations that should have stayed in the house were being indexed into the shared shelf. Nothing left my machines, but the wrong readers could have seen them. I purged the collection, rebuilt it from a clean sweep, and the guard now matches on the full path instead of a name I remembered from memory. Fifty four files were skipped on the first run under the new guard. I had been right about the risk and wrong about the check.

The second was a label. In my picker, several of the largest models appear through the same local doorway as the small ones. Same menu, same address, same little green dot. They are not local. They run on a cloud account, and the local software is just forwarding to them. One of them, a hundred and twenty billion parameter model with cloud in its name, was a single click from being handed the private shelf because of where it sat in the list. Local is not a place in a menu. It is a claim about where the bytes go, and you check it at the wire, not at the label.

The third was a lie of convenience in the software's own bookkeeping. The export I was using to list every model returned only the ones I had personally configured, not the whole table, so my inventory was wrong while looking complete. And the field named messages, the one you would obviously read to get a conversation, was not the conversation. The real thing was a tree of turns stored somewhere else. If I had trusted the names, the diary would have been summarizing the wrong transcript every night and telling me it was fine.

What changed

By the end of the day the numbers were these. Three hundred and twenty three vault files indexed. A hundred and eleven notes on the private shelf, including the manual. Fifty five models carrying the same standing instruction about what they know and what they are not allowed to guess at. And a night shift on the calendar for twenty past eleven, every night, that needs nothing from me.

The word I used when the last check came back clean was perfect, and I do not use that word about my own systems. What I meant was narrower and better. For the first time, every model I own starts the day where I left off, and the ones that should not know certain things do not, and I can prove both.

Fifty five models and one memory, with a bright line through the middle of it that says who gets what.

Memory turned out not to be a feature. It is a privilege, and the whole build was really just a list of who has it.

If you are wiring a memory into anything with more than one reader, write the list first. Who can see what, and how you will know if that stops being true. The plumbing is an afternoon. The list is the product.

MG