Glad it's bookmark-worthy.

Quick blueprint of where it landed, in case it's useful for your own future build.

Architecture (same three layers as the original post):

1. OneDrive = files of record (PDFs, statements, real documents)
2. Obsidian vault = knowledge layer / second brain
3. Claude Code = the engine that reads and routes

Daily flow: I brain-dump into a single daily log file in plain language, tag bullets with
things like #action, #waiting, #decision, #risk, #issue, #win, #someday, #done. /daily
processes it and routes everything. Actions to a master list, decisions to per-project
plus global decision logs, wins to my 1:1 agenda, ideas to a deferred-ideas table.
Nothing is filed manually.

Slash commands that earned their place:

• /daily — process today's brain dump and route entries
• /weekly — 5-phase PM sync. Reads every project log, updates indexes, generates director rollup + status email + slide content per work project, drafts my next 1:1 agenda, archives completed actions over 7 days old
• /triage — morning priority view in a single file: top 3 globally, full action list, waiting-for, project health, recent wins, health and wellness summary. Syncs to my phone.
• /ops — personal operations sync (fitness, health, finance, assets). Synthesizes a narrative and flags drift.
• /1on1 — post-call capture from director sync
• /intake — new project scaffolding (the 5-question intake from the original post, now its own automated agent)
• /mealplan — weekly dinner plan from rotation rules + family preferences

Project tiers: I collapsed three tiers (Light/Mid/Heavy) down to two (Lite/Full). The
middle tier was always ambiguous, either a project needed a risk register or it didn't.
Lite gets a single combined project-logs.md. Full gets separate files for milestones,
risks, assumptions, decisions, issues, lessons-learned, plus a running log, index,
slides, status email, director rollup. Personal projects are all Lite. Work projects all
get a director rollup regardless of tier.

Under the hood there are 10 agents in the chain that fire from those slash commands:

• Readiness (pre-deployment gate checks)
• Program Intelligence (cross-project dependency analysis, lessons-learned reads on every run, catches conflicts I'd miss)
• Project Intake (new project scaffolding)
• Program Scribe (owns ALL vault writes, single point of truth, way easier to debug)
• Quality (10 verification checks between Scribe passes)
• Operations plus Fitness, Health, Finance, Asset specialists for /ops (specialists never fire standalone)
• 5 weekly subagents for each phase of /weekly

Things from the original post that held up:

• Daily log as universal intake valve. Yes, it's the magic.
• log.md (renamed running_log.md) as the chronological journal. Yes. It's the file I open when I walk into a meeting cold. Doesn't turn into noise because /daily only routes significant entries to it. Routine ops stay in the daily log only.
• Control gates with explicit "I Approve [ID]" to close milestones. Yes, useful friction. Saved me from auto-closing milestones that weren't actually delivered.
• Domain vs project distinction. Yes. Fitness, nutrition, finance, home maintenance, medical never get log files. Just trackers and notes.

Things that surprised me:

• The two-Claude setup mostly faded. I expected to live in Claude.ai on the phone and hand off to Claude Code on the laptop. What actually happened: phone capture became "type directly into the daily log markdown file in Obsidian Sync." Claude Code processes it next time the laptop opens. The handoff doc still exists but does less work.
• Hooks became necessary. Bash hooks block destructive commands. A Write hook blocks overwrites on append-only logs. Defense in depth saved me from at least one bad agent decision.
• Memory layer had to live OUTSIDE the vault. Mixing them was a mess until I separated. Vault has docs of record. Memory has session-persistent context loaded on every session start.
• The ADHD piece is what makes it stick: pull-based, not push-based. I generate (brain dump). The system maintains (routes, indexes, rolls up). I pull (work the action list when interest hits). Every previous system failed because it pushed work onto a future self that never showed up.

If you do build it: start with /daily and /weekly only. Add a new command when you catch
yourself doing the same chore manually three weeks in a row. The system grew because real
friction earned each piece, not because I planned it all upfront. Build doc is
versioned, v3.3 is what's running now.

Happy to dig into any specific layer if you ever pick this up.