--- name: post-2-8-0-brain-dump description: "CLOSED — the planning file for the Claude Brain Dump. The dump was written and lives at library/BRAIN_DUMP.md. Kept for the standing rules the owner locked in about who writes it, who it's for, and keeping it current." metadata: node_type: project originSessionId: 0b7c5f41-bb34-4ab4-93be-fdb363f5eb40 --- **CLOSED — the brain dump was written.** It lives at **`library/BRAIN_DUMP.md`**. This file was the planning and sequencing debate about when to run it; that debate is over. *Reduced 2026-07-20: the placement argument, sequencing chain and version-tagged ordering were removed as dead queue state. The file previously asserted the dump would land at a different path than it actually did.* **What it is:** the owner's prepared prompt asked for a comprehensive record of Claude's **understanding** of RobCo — vision, philosophies, architecture, roadmap, standards, patterns, **intentionally-avoided things**, lessons, **inferred unwritten rules**, recurring themes — written so that understanding could be reconstructed if all memories vanished. Not a restatement of the docs. Where docs conflict, resolve toward **the philosophy the project actually evolved toward.** **Why it exists (the reasoning worth keeping): it is a SAFEGUARD against memory loss.** Context compaction has genuinely been happening — this is a real risk, not a hypothetical one. ## ⭐ STANDING RULES the owner locked in (2026-07-08, *"fold in all 5"*) 1. **It lives in the library and is registered in the always-loaded pointer index**, so sessions auto-find it without being told. 2. **Its audience includes future Claude/Dispatch SESSIONS, not just a new human engineer.** 3. **Accuracy: verify against CURRENT code where it matters** — memories are point-in-time and stale-prone — and **explicitly flag INFERENCE vs known fact.** 4. **It is a LIVING DOC.** Architecture/implementation sections are marked as current-state and **refreshed after any structural refactor, BEFORE new work builds on the new structure.** The vision/philosophy sections stay stable; only the structural sections churn. 5. **Dispatch LEADS the vision / inferred-rules / lessons parts** — that understanding comes from accumulated cross-session context and memory, and **a fresh session is context-blind.** Run on Opus with full memory + planning + repo access.