โ† Back to system overview
Subsystem deep-dive

The Brain Vault

The shareable knowledge base: an Obsidian vault organized PARA-style, version-controlled in git, with strict rules about what lands where. The thing every other layer reads from.

0
Notes
0
Sessions logged
0
Active projects
0
Git commits
The layout
PARA, with a place for everything

A documented folder map (MAP.md) is the source of truth for where things live, so the structure survives even when Claude is the one moving files.

๐Ÿ“ Projects

Active, outcome-oriented work: pitches, builds, decisions.

36 notes

๐Ÿ“š Resources

Reference material: articles, news digests, podcast summaries.

graph-visible

๐Ÿ›  Stack

AI-stack build notes and these architecture diagrams.

system notes

๐Ÿ“ Sessions

Session-close logs. The running record of work.

131 notes

๐Ÿ” Reviews

Weekly reviews and monthly rabbit-hole sweeps.

generated

โšก AI/Skills

Source of truth for personal skills.

19 skills
The routing protocol
Four streams, never tangled

Keeping content properly routed is what stops a second brain from feeling like a junk drawer.

Project synthesis

Pitches, status, decisions โ†’ Projects/ + Sessions/. Graph-visible.

Consumed content

Articles + podcast summaries โ†’ Resources/. Lean twins are graph-visible; full transcripts stay out.

System notes

How the machine works โ†’ Stack/, AI/Skills/, MAP.md.

Identity docs

Who you are โ†’ Context/. The single canonical home; never duplicated.

Version control
Git is the memory of what changed
The biggest tributary
The podcast pipeline

Most of the vault's volume is automated listening: episodes fetched, enriched, summarized, and split into graph-friendly twins.

3,404 lean summaries

Each episode gets a transcript-free twin in Resources/Podcast-Summaries/ (graph-visible), while the heavy full transcripts stay ignored.

Per-show citations

A scraper pulls each episode's reference list into the note, so sources land in the graph too.