A Vault That Holds

Every educator I know has, somewhere, a graveyard of notes: a folder of brilliant fragments they will never find again. The problem is rarely a lack of tools. It is a lack of rules — a stable architecture the notes can settle into. After several rebuilds of my own system, I have stopped chasing the most powerful setup and started keeping a small number of principles that hold under daily weight. Here are the ones that survived.

Few and stable beats many and clever

The instinct, whenever a system feels weak, is to add: another plugin, another tag scheme, another layer. It almost always makes things worse. Complexity has to be carried by a tired person at the end of a teaching day. So the first rule is restraint: prefer a few stable rules to many clever ones. A system you can explain in one breath is a system you will still be using in a year.

Then, give each mechanism one job. Folders decide the broad where. Structured fields (the metadata at the top of a note) decide state — what is active, what is waiting, what is done. Tags do light semantic work and nothing more. The failure mode is asking tags to carry classification, state, and meaning all at once until they carry none of it.

Don't reorganize the old notes until the new standard is stable. Migration before a rule is just rearranging the graveyard.

The desk is not the archive

A daily note is a workbench: it captures and it drives the day. It is the worst possible place to store anything important, because tomorrow buries it. So the third rule: capture on the desk, but let anything that matters flow back to a project, an area, or a reference note where it can be found on purpose. A capture surface and an archive are different organs; fusing them is how good notes disappear.

Build the template before the migration

The most expensive mistake is reorganizing hundreds of old notes before the new standard has proven itself. You will change your mind in week three and have to redo all of it. Define the template, live with it on new work, let it earn trust — then migrate, and only what you actually reach for. A homepage, finally, should answer four questions and resist the urge to do more: what should I do today, what is in motion, what is waiting on me, and what needs a second look. A vault that answers those is a vault that holds.