Standard::Vault
The norm of the ground. A vault is a folder of plain files that remains
perfectly readable if every tool around it disappears. These norms exist so
that promise holds: name things one way, describe them one way, journal one
way — and any human or machine can navigate the vault in Finder, Obsidian,
or a terminal, forever.
This book defines what must be true of a Standard vault. How the framework
implements these norms (the vault loader, the press) is documented in the
Framework reference — the implementation conforms
to this book, never the other way around.
Sections
| § | Norm | What it fixes |
|---|---|---|
| 1.1 Naming | kebab-case, no exceptions | files findable by guessing |
| 1.2 Frontmatter | one property set, keys = design tokens | metadata that machines and themes can trust |
| 1.3 The journal | Logs/yymmdd.md, time headings |
a diary any tool can append to |
The one law behind every section
File over app. Information lives in raw, open files. Applications are
interchangeable readers. Deleting a tool must never alter or lock the data.
Everything else in this book is a consequence of taking that law seriously.