Give your AI a second brain.

Your AI is clever enough. What it’s missing is you. Here’s how to give it your work, your decisions and your history, in plain notes you own.

Free guide · Obsidian + Claude · built and used every day

The short version, with diagrams. About ten minutes.

01 The problem

Every chat starts from zero.

Your AI is clever enough. What it doesn’t have is you: your business, your decisions, what happened last week. So you explain it again, every time.

Without a second brain
  1. Monday“So, my business is… my customers are… last week we decided…”
  2. Tuesday“So, my business is… my customers are… last week we decided…”
  3. Wednesday“So, my business is… my customers are… last week we decided…”

You explain yourself again. Every session.

With a second brain
me.md_active.mdBrand voiceToday’s note
“Morning. Your #1 today is the proposal. The pricing call from Tuesday is still open.”

It reads your notes first, so it already knows.

02 The idea

A folder of notes your AI can read.

Obsidian is a notes app that sits on top of an ordinary folder. Every note is a plain text file on your own computer. Point your AI at that folder and it can look things up before it answers.

  • Plain textNo lock-in. If the app disappeared, your notes wouldn’t.
  • InstantLocal files read in milliseconds, so checking five notes costs nothing.
  • One source of truthEvery project reads the same notes. Update once.
  • Linked[[Links]] between notes let the AI follow a thread the way you would.
03 How it fits together

Four layers.

The folders are the easy part. What makes it work is what sits on top of them.

  1. 04RoutinesScheduled jobs that write the brief and keep things tidy.
  2. 03SearchThree ways to find anything, used in a fixed order.
  3. 02OrientationFour short files a new session reads first.
  4. 01The vaultA folder of plain notes. Where everything lives.
04 Layer one

The vault.

Eight folders cover almost everything. The names matter less than keeping them consistent.

  • AreasOne per business or role, each with its _context/ docs
  • Daily logsOne note a day. The brief lands here
  • ProjectsOne file per project, plus _active.md
  • KnowledgeYour processed thinking: books, people, themes
  • Meeting NotesSummaries and transcripts, synced in
  • NotesEvergreen how-tos and reference
  • SourcesRaw clippings. Read-only
  • _SystemOrientation files, routines, templates

The one idea to steal

Each business gets a _context folder: brand voice, customers, positioning. Write each document once. Every project reads it; none of them copies it.

_context/Brand voiceWritten once
  • Website project
  • Sales emails
  • Social posts
05 Layer two

Four files it reads first.

A new session gets its bearings from four short files: who you are, where things live, what it can do, and what’s happening now.

Start/vault-start
  1. 1me.md
  2. 2Vault Map
  3. 3Skills Map
  4. 4_active.md
Work

It already knows who you are, what you’re building and what’s next.

Close

Update _active.md: what happened, what’s next, what needs you.

The next session starts where this one ended.

06 Layer three

Three ways to search, in order.

Give an AI one search tool and it reads everything. Give it three and a rule about which comes first, and it finds things fast.

  1. 1Obsidian CLIStructure“What links to this project?”
  2. 2grepExact words“Find ‘invoice 2231’.”
  3. 3Semantic searchMeaning“Have I written about pricing before?”
07 Layer four

It works while you sleep.

A few scheduled routines turn the folder into something that runs. Each one is just a note describing a job, so it goes wherever you go.

  • 07:00Morning briefCalendar, emails from people, priorities, what’s gone stale
  • All dayYou workDrop [FB+] and [FB-] notes to tune tomorrow’s brief
  • 22:00Night shiftDigest new clippings, add links, refresh search
Every Sunday
Weekly review: what moved, what’s slippingHealth check: broken links, stale notes
08 Trust

Always know who wrote what.

Once an AI writes in your notes, you can lose track of which thinking is yours. A one-word label on every note fixes that.

  • source: meYour own thinking
  • source: aiWritten by the AI
  • source: ai-summaryAI summary of a meeting
  • source: transcriptWord-for-word capture
  • It never edits your words, only adds tags and links.
  • Clipped articles are read-only.
  • Every change it makes is logged.
09 If you do client work

Give clients their own vault.

If a client gives you an AI account they manage, their admins can see what it reads. Their data may also include other people’s personal details. So keep it separate: one status line crosses over, nothing else.

Your vault
Your AI account
  • Journals
  • Your businesses
  • Other clients
  • Morning brief
One status line
crosses
Nothing else
Client vault
Their managed AI account
  • Client docs
  • Customer data
  • Own search index
  • Own session state
10 Learned the hard way

What actually breaks.

  1. 01

    Read your calendar through the operating system

    Scripting the calendar app is painfully slow and returns the wrong dates. The system’s own calendar framework is instant and correct.

  2. 02

    A 7am job needs a laptop that’s awake

    Schedule a wake-up just before, stop it running twice, and catch up if it missed.

  3. 03

    Let every routine fail gracefully

    Put a timeout on everything. A slow email check should shorten the brief, not kill it.

  4. 04

    Search can break silently

    Update your tools and semantic search can stop working without an error. Check it after every upgrade.

  5. 05

    Close every session

    If _active.md goes stale, every new session starts cold again. It takes thirty seconds.

11 Getting started

Don’t build it all at once.

This setup grew over months. Build it in stages and use each piece before adding the next.

  1. Day oneThe folders, one _context doc, me.md, and the global config.
  2. Week oneThe Vault Map, the search ladder, and a three-line daily note.
  3. Week twoThe morning brief. Make it reliable before adding anything.
  4. Month oneWeekly review, health check, night shift, source labels.

You’ll know it’s working when you stop explaining background before asking for things.