# VAULT INDEX

**Read this file, not the whole vault.** This is the map. Your notes vault may run to hundreds of
notes — loading them all burns context for nothing. Use this index to find the ONE folder you need,
then open only those notes.

Pairs with `CLAUDE.md` (the rules file, loaded every session) — this file is the opposite: records,
loaded only on demand. Put it at the root of your notes vault (Obsidian, plain folder, whatever you
use) and keep it short enough to read in one pass.

---

## Who this is

**[Your name]** — [one line: what you do, where you're based].

[If you run more than one brand/project/entity, list them here so the agent doesn't confuse them:]
- **[brand/project A]** — [what it's for].
- **[brand/project B]** — [what it's for].

[One paragraph on how the work actually flows, if that's non-obvious — the thing a new agent
session would otherwise have to reverse-engineer from scratch.]

⚠️ [Any standing caveat worth repeating: e.g. "numbers in these notes are point-in-time — verify
against the live system before acting on any of them."]

---

## The map

| Folder | What's in it | When to open it |
|---|---|---|
| **[Folder A]/** | [What lives here, roughly how many notes.] | [The question that sends you here.] |
| **[Folder B]/** | [What lives here.] | [When to open it.] |
| **[Folder C]/** | [What lives here.] | [When to open it.] |

**Root notes:** [Any standalone files worth naming directly — a dashboard, a running log, a
do-not-contact list — with a one-line reason to open each.]

---

## Rules for using this vault

1. **Never bulk-read.** Open the folder this index points to, nothing more.
2. **The vault is notes, not truth.** If there's a live system of record (a database, a CRM, a
   production app), that's the source of truth — these notes lag it and can be wrong.
3. **This index is a map, not a mirror.** When a folder's purpose changes, update the one line
   here — don't paste the folder's contents in.
4. **Related but separate:** `CLAUDE.md` + `memory/` cover *how the code and systems work* and
   load every session. This vault covers *what happened* — the people, projects, and decisions.
   Use memory for "how do I", this vault for "what happened with".