brain-rebuild

Brain Rebuild

Redesigns the qmd schema based on what the wiki actually contains today, then rebuilds the index from scratch. Destructive — wipes existing collections/contexts and their embeddings. Always get explicit user approval before applying changes.

When to Use

• The wiki has grown and the current single wiki collection no longer matches how the user searches
• The user wants finer-grained contexts (e.g. distinct context descriptions per sub-folder)
• After significant reorganization of wiki/ or raw-sources/ folder structure
• Never as a routine refresh — for that, use /brain-refresh

Procedure

All commands run from the vault root.

Step 1 — Survey the current state

• Read scripts/qmd/setup.ts to see the current collections and contexts
• Read CLAUDE.md to understand the documented schema and any references to collection names
• List current state from qmd:

  INDEX_PATH=.qmd/index.sqlite pnpm dlx @tobilu/qmd collection list
  INDEX_PATH=.qmd/index.sqlite pnpm dlx @tobilu/qmd context list
  INDEX_PATH=.qmd/index.sqlite pnpm dlx @tobilu/qmd status
  

Step 2 — Analyze the wiki

• Glob wiki/**/*.md and raw-sources/**/*.md
• Read enough pages (especially wiki/index.md and wiki/overview.md) to understand actual topic clusters, page-type distribution, and folder structure
• Identify natural groupings: by domain (e.g. ml, distributed-systems, finance), by page type (topics vs entities vs qa), by source provenance, etc.

Step 3 — Propose a new schema

Produce a recommendation that includes:

• Collections — name, root path (relative to vault), file glob pattern. Justify each split.
• Contexts — global context, plus per-collection and per-subpath context descriptions. Each context should be a one-sentence description that helps a future search disambiguate between similar pages.
• Migration impact — what changes for /brain-ingest, /brain-search, /lint, and CLAUDE.md (e.g. if collection name wiki becomes wiki-topics, all -c wiki invocations break)