Systems · Content operations
The Docket
Boring on purpose. Boring is what still works in five years.
What it isn't
There's no CMS. No database. No admin login, no plugin directory, no monthly seat charge: no editing surface on the web for anyone to get into. I've spent enough of my career inheriting systems that a vendor stopped supporting to be suspicious of anything with a login screen and a roadmap.
What it is
- Markdown files in version control. Every page and every entry is a text file. The history of this site is a commit log — I can see what changed, when, and why, and put any of it back.
- A static build. The pages compile to plain HTML and CSS ahead of time, so no server assembles a page while you read it. A few figures run small scripts in your browser (the brain graph is drawn live), but there is no application behind them, which is why it's fast and why there's little to attack.
- No third parties. The fonts are served from this domain, not a font network. No embedded video, no third-party widgets, no ad trackers. The one measurement is the host's own cookie-free page analytics, which counts visits without following anyone anywhere.
- One gate. A change becomes a branch, the branch builds a preview, and I look at it. Nothing reaches the live site without me having seen it on the page it will actually appear on.
The bridge from the vault
The second brain and this site share a spine. When something I've captured is worth passing along, I flag it in the vault; a queue collects the flagged items and drafts a one-line note for each. I approve them one at a time — individually, not as a batch — and the approved ones become entries on the shares page. The same path redraws /now/.
The rule that matters is what doesn't cross. Only the entry travels — a title, a link, a date, a line of my own. The captured material itself never leaves the vault, and anything marked confidential is excluded from the queue before I ever see a draft. The bridge is deliberately narrow, because a wide one would eventually carry something it shouldn't.
Why it's built this way
Same reason as everything else here. A system you can't inspect is a system you're trusting on faith, and I've watched too many quiet failures to do that with anything that has my name on it. Plain files, visible history, one gate, no moving parts I can't name. It'll be readable in a decade, which is longer than most of what I've replaced lasted.