How it's actually built

Four layers

Each is simple on its own. The system is what happens when they're wired together.

• Capture. Dedicated intake channels — a vault email address, feeds, video transcripts, document scans, saved articles. Nothing is skipped and nothing is judged at the door. Everything lands in one staging area as an enriched note: summarized, tagged, and linked to whatever it relates to.
• Routing. A router files each capture to its home against a written rulebook — the rulebook is a document I edit, not code I have to change. Sensitive categories get flagged, fenced from anything external, and recorded in an audit log I read after the fact rather than approving one at a time.
• Domains. Each area of life has its own folder tree, its own hub note, and its own cadence. Some refresh daily. Some refresh only when something actually changed, which is most of them.
• Surfaces. The system writes upward into a small set of dashboards — a morning briefing, a command center, status boards. The day starts pre-briefed instead of starting with an inbox.

Why plain text

Every note is a markdown file on a disk I own, in version control. No database, no proprietary format, no vendor who can change their pricing or their mind. If every tool I use today disappeared, the notes would still open in any text editor made in the last forty years. That constraint has cost me features. It has never once cost me data.

The parts that were harder than they looked

Routing confidence. The first version filed everything, confidently, including the things it had no business being confident about. The fix wasn't a better classifier — it was giving the router permission to fail. Anything it can't place goes to a queue for me instead of being forced into the nearest folder. A system that admits uncertainty is worth more than one that's usually right.

Silent success. Early on, every completed job announced itself. Within a week I was ignoring the notifications, which meant I was also ignoring the failures. Now a successful run writes a log nobody reads and a failed one raises an alert on a dashboard I actually look at. Attention is the scarce resource, not compute.

Canonical location. The hardest rule to hold. It's always easier to write a second note than to find and update the first one, and the cost shows up months later when two documents disagree and you can't tell which one you trusted. This is the rule I break most and regret most.

Knowing when to stop. A system that manages your life is unusually good at generating work for itself. The grading question I ask now is not "could this be better" but "is this done — maintain only," which in my world is the highest state a system can reach.

What it doesn't do

It doesn't send anything. It doesn't spend anything. It doesn't publish anything. It doesn't decide anything that would be expensive to undo. It drafts, files, links, and surfaces — and every one of those is reversible with a text editor and thirty seconds. The blast radius is the design, not an afterthought.

← Back to the overview · The publishing side of the same system is here.