brain-reviewlisted

# Brain review (5–10 minutes, weekly) Steps 0–9 run every week; "Not every week" has its own triggers. Missed weeks are normal — catch up in batches, never scold. **Conventions:** `<vault>` = the path from the `Brain vault:` line in your global rules; with no such line, the folder this session started in, provided it holds a `CLAUDE.md` with a mode line; only if neither exists, `~/Brain`. `python3` = your working python command (on most Windows machines `py -3`; the global rules name it). ## Every week 0. **Load the vault rules first:** `<vault>/CLAUDE.md` (schema, note anatomy, vault language, mode, red line) and `<vault>/index.md` if present. No `CLAUDE.md` → wrong path or unfinished setup: say so and stop. 1. **Inbox to ZERO** (hard rule): process every file DIRECTLY in `<vault>/00-inbox/` — never the kit's `Inbox rule.md`, `index.md`, `CLAUDE.md`, never `raw/` (`brain-ingest`'s queue). One file may take SEVERAL exits (a decision + two dates + a question = four). - **(a) a note:** paraphrase it (frontmatter, vault language, matching `_templates/` file, real values for placeholders); file by ACTIONABILITY: project → `10-projects/` · area → `20-areas/` · **settled question → `40-decisions/YYYY-MM-DD-slug.md`**, append-only · keeper knowledge → `30-knowledge/` · person → `30-knowledge/people/` (facts only, in EVERY mode — role, what was agreed, what they are working on; never a judgement of character, mood or motive. Test: *could I show t