The AI second brain

The problem

I run a public organization, a growing business, a family, and a homestead — all at the same time. Each of those generates paper: email, meeting notes, filings, newsletters, receipts, manuals, ideas. For years the paper won. The work of managing information was crowding out the work of using it.

The idea

The system is a plain-text vault — a few thousand markdown notes organized by domain — with an AI agent operating it on a schedule. Not a chatbot I ask questions; an operator that does the filing. The division of labor is strict: the system handles capture, routing, and refresh; I handle judgment. Anything irreversible or outward-facing waits for my sign-off.

The architecture

Four layers, each simple on its own:

• Capture. Dedicated intake channels — a vault email inbox, RSS feeds, video transcripts, document scans. Everything lands in one staging area as an enriched note: summarized, tagged, linked.
• Routing. An automated router files each capture to its home — work, personal, reference, projects — following a written rulebook. Sensitive material is flagged and fenced off from anything external.
• Domains. Each area of life has its own folder tree, its own hub note, and its own cadence — some refresh daily, some weekly, some only when something changes.
• Surfaces. The system writes upward into a small set of dashboards — a morning briefing, a command center, status boards — so the day starts pre-briefed instead of starting with an inbox.

The operating principles

• Failures loud, successes silent. A job that breaks must announce itself; a job that works shouldn't need attention.
• One canonical location per concept. Duplication is where systems rot.
• Implementation precedes documentation. Working things first, write-ups second.
• The human owns the blast radius. The system proposes; anything with real-world consequences waits for me.

What actually changed

The honest answer: my mornings. The reactive triage that used to eat the first hours of the day happens overnight, unattended. Decisions come to me framed, with the context attached. The paper still exists — but now it files itself, and I spend the attention it used to cost on the work that matters.

Colophon: this site is itself an output of the system — planned in a structured interview, designed by the system's design agent from my brand tokens, built and verified by the system, with me approving three gates along the way. The proof of a working system is what it ships.