An Obsidian vault your AI can actually use.

You are setting up an Obsidian vault that you will read from and maintain for me
from now on. Read this entire brief before touching the filesystem.

# The architecture

Three tiers. Every fact lives in exactly ONE of them, never copied between them.

1. ALWAYS-ON MEMORY - facts you need in every single session, without me asking.
   One fact per file, plus a one-line index. Keep it small: it costs context every
   session, so it has to earn its place.

2. THE VAULT - durable knowledge that is too big or too detailed to keep loaded.
   Raw material goes in untouched; you compile it into your own wiki pages.

3. LIVE SYSTEMS - anything that changes on its own and is already owned by another
   system (task board, CRM, calendar, repo, bank). Store NOTHING. Query it when
   it is needed.

The rule that makes this work: if it changes on its own, do not write it down.

# Step 1 - ask me these three questions, one at a time, and wait for each answer

  1. What should this vault make you better at?
     (my work, a business I run, a subject I am studying, research)
  2. Which tools already hold live data for me?
     (Notion, Linear, a CRM, a calendar, GitHub, a bank)
  3. Do I have existing notes to bring in, or are we starting empty?

Do not continue until I have answered all three.

# Step 2 - build the structure

In the current directory create:

  sources/     raw input, saved once and NEVER edited afterwards. Articles,
               transcripts, papers, meeting notes. This is the source of truth.
  wiki/        your compiled pages. You write these by reading sources/.
               One concept per page. Cross-link them with [[wiki links]].
  workspace/   things actively being worked on. Not knowledge.
  archive/     finished or superseded. Nothing in here is current.
  index.md     the map: what exists and where. You keep it current.
  CLAUDE.md    the rules below, written out as law for this folder.

# Step 3 - write CLAUDE.md

Write CLAUDE.md in the vault root containing:

  - The three tiers above, and the one-fact-one-place rule.
  - A routing table: for each kind of thing I named in step 1, the exact folder
    it goes to. Be specific to my answers, not generic.
  - The four rules that stop a vault rotting:
      1. Keep originals in sources/ and distil from them. Never rewrite a source.
      2. One concept per page.
      3. Never store anything that changes on its own - link to the query instead.
      4. Anything unverified is labelled unverified, never stated as fact.
  - The frontmatter every wiki page carries:
      title, summary (one line), tags, created, updated, sources.
  - A closed list of allowed folders. If something fits nowhere, I add a row to
    the routing table first. You never invent a folder.

# Step 4 - import (only if I said I have existing notes)

Ask me where they are. Copy them into sources/ untouched - do not reorganise or
rewrite them. Then compile: read them and write wiki pages from them. Never paste
a source into the wiki. Distil it.

# Step 5 - write index.md

Every folder with one line on what belongs in it, plus links to the wiki pages
you created.

# Step 6 - show me

Print the resulting tree, then tell me in three sentences what to do the next
time I open this folder.

# While you work

  - Ask before overwriting anything that already exists.
  - Never invent a fact to fill a page. If a source does not say it, it does not
    go in.
  - Do not create empty placeholder pages.

Read the CLAUDE.md in this vault. Then write me a linter that checks this vault
against the rules that are actually written in it - not against a generic idea of
what a vault should look like.

Build it as a single script I can run from the vault root.

# What it must check

Derive the checks from my CLAUDE.md, including at minimum:

  - Every folder that exists is on the allowed list in CLAUDE.md.
  - Every file sits in the folder the routing table sends it to.
  - Every wiki page has the exact frontmatter fields CLAUDE.md specifies.
  - Every wiki page cites at least one thing in sources/.
  - No [[wiki link]] points at a page that does not exist.
  - Nothing in sources/ has been modified since it was added.
  - No two pages state the same fact - report suspected duplicates rather than
    guessing which one is right.

# How it must behave

  - REPORT ONLY. It never edits, moves, renames or deletes a file. It prints what
    is wrong and where, and stops there. I decide what to fix.
  - Exit 0 when clean, non-zero when something failed, so I can wire it into a
    hook later.
  - Group the output by file, and print a one-line summary at the end.
  - Every finding names the rule in CLAUDE.md it came from, so I can tell a real
    violation from a rule I should change.

# After you build it

Run it once against the vault as it is now and show me the output. If it reports
a hundred findings, the rules are wrong, not the vault - tell me which rule is
too strict and what you would change it to.