Second brain: notes, PARA, and knowledge graphs

A note system agents can actually use:

• Stable paths and naming so retrieval is deterministic.
• PARA-style or equivalent structure: Projects, Areas, Resources, Archives—pick one and enforce it.
• Links between notes and tickets so “what we decided” survives turnover.

Shoutouts about “second brain in WhatsApp” are really notes + channel—the hard part is discipline, not the messenger.

• Graph and memory features (where configured) pair with structured notes.
• Skills can encode how to create, move, and retire notes—reducing chaos.
• Local-first fits vaults that should not live in a random cloud notebook by default.

1. Freeze a minimal schema: frontmatter fields, link conventions, tag rules.
2. Ingest only what you will maintain—archive aggressively.
3. Nightly or weekly review: orphan notes, duplicate titles, broken links.
4. Ground agent answers: cite note paths for non-obvious claims.
5. Migrate legacy piles in batches—not “import everything” day one.

• Backup strategy for your vault—agents can destroy as well as organize.
• Sensitive note boundaries: HR, health, legal in separate vaults if needed.

1. Inventory top 20 notes you touch monthly—make those pristine first.
2. Add MOC (map of content) pages for dense areas.
3. Wire one capture path from mobile into Inbox.
4. Automate only boring moves (filing templates)—not judgment calls.
5. Measure time-to-find for common questions.

• “Find contradictions between these two notes on topic X.”
• “Propose merge or archive for this orphan cluster.”
• “Summarize decisions from last week’s meeting notes with links.”

• Restore test from backup succeeded.
• Permissions prevent agents from reading executive-only vaults.
• Style guide is one page—people actually follow it.

• Note hoarding—agents accelerate accumulation of junk.
• Fragile auto-links that break on rename.
• Two systems: chat memory contradicting markdown truth.
• Privacy: pasting vault contents into the wrong model region.