What's sacred is your content, not the folder it lives in

Every system that lives long enough has to update itself, and updates are where trust is won or lost. You are being asked to let a program reach into files you care about and change them. So the question I had to answer before building the update mechanism was a simple one: what is it allowed to touch, and what must it never touch?

My first answer was a folder. Your personal side of the system lives in one place, and the early rule was blunt: the updater never touches that folder, full stop. Clean, easy to reason about, easy to promise.

It was also wrong, and I found out why the first time an update needed to add something new to that folder. A later version introduced a kind of note that routes between your projects, and to support it, your side of the system needed a file it didn’t have before. The blunt rule forbade exactly that. Protecting the folder meant the system could never grow.

So I had to sharpen the rule from a place to a thing. What is actually sacred is not the folder. It is your content: your answers, your decisions, the specifics of how you work. That can never be changed, deleted, or guessed at by an update. But the structure around it, a new file, a new column, an empty slot waiting to be filled, can be added, because adding an empty slot takes nothing away from you.

So an update here is only ever allowed to add. It can create a file you didn’t have. It cannot touch a value you wrote. Any change that can’t be expressed as “check what’s already there, then add only what’s missing” is treated as a change I don’t understand well enough to ship yet. Before any of it runs, the system takes a full snapshot, so if something goes sideways the fix is to copy your old state straight back, not to rebuild it from memory. And nothing happens without your yes. “Later” is always a complete answer.

The idea I gave up was that safety means never touching anything. It doesn’t. A system that can’t change is one that slowly stops being useful. Real safety is knowing exactly which things are yours, and building so those specific things are the ones that can never be harmed, while everything around them stays free to improve.