digest
Short Summary
Main recommendation: Build a persistent "AI second brain" by paying for a pro AI plan, storing your knowledge in an Obsidian vault of linked markdown files, defining your AI's identity through three files (user.md, soul.md, identity.md), organizing the vault into a fixed folder structure, feeding it meeting and daily data, and running a nightly process that consolidates and links the notes. The speaker says this setup lets AI draw on your context so it can act for you and "buy back days of your life."
Key Points
- Paying for a pro AI membership is the first step, because free versions are slower and run older models.
- Obsidian is the speaker's preferred storage tool, since it saves notes as readable markdown and its graph view shows connections; he presents Google Drive, Notion, and Obsidian as three options, noting it's personal preference, with Obsidian being a step up.
- Defining identity files matters: user.md describes you, soul.md sets the AI's voice and values, and identity.md defines its role.
- Organizing the vault into seven folders (People, Projects, Decisions, Companies, Meetings, Daily, Knowledge) reportedly raised question-answer accuracy from 60% to 85%, according to the speaker.
- A nightly consolidation process (manual or automated) finds orphan notes, merges duplicates, updates links, and flags items for review.
Details Worth Noting
- Concrete instructions:
- Install Obsidian (the speaker's recommendation; he says "just start with Obsidian" and that having AI create the second brain takes about 5 minutes).
- Create three identity files: user.md (who you are, role, communication style, frameworks, principles such as theory of constraints and minimum effective dose), soul.md (instructions on voice and tone, e.g., "be direct, challenge me with love, no hedgy words, avoid 'try,' 'hope,' and 'maybe,' solve problems before asking"), and identity.md (the AI's role, e.g., part coach, part chief of staff, part accountability partner).
- Have an AI interview you about how you work, what you value, and how you communicate, then have it draft the three files, save them, and point your AI to them.
- Create seven vault folders: People (a file per person), Projects (timestamped, with context), Decisions (what was decided, how, and the alternatives), Companies (research and competitors), Meetings, Daily (3 to 5 lines per day summarizing decisions), and Knowledge (reusable insights, frameworks, quotes).
- Optionally add a MOC (Maps of Content) folder that consolidates related files into summary references, built once a topic gets messy.
- For meetings, use a transcription tool such as Granola with a custom extraction template that outputs decisions (what, by whom, why), commitments (who promised what, by when), preferences, and key insights as markdown, skipping small talk, saved into the Meetings folder by date and meeting name.
- Nightly processing prompt: "Read everything that I've added to my vault today. Find orphan notes and mentions of people, projects, and companies that don't have their own files; create those files. Consolidate duplicates. Update the relevant Maps of Content with new links. Flag anything strategic for me to review tomorrow." Run it manually each day or automate it with a scheduled task (the speaker uses Claude's scheduled tasks as a cron job).
- The speaker says the knowledge base works by links: a request like "send the invite to John" works because "John" has the most links in the vault, linking to his email and phone number.
- The speaker frames the core idea as "you improve your brain at the speed of links," and says the system points back to raw files rather than storing everything.
Bottom Line
A usable AI second brain depends less on the AI tool itself and more on well-structured, linked notes plus clear identity instructions that the AI can reference every time.
