brain-initlisted

# Brain Init — Session Context Loading (post-C1) ## When to use - Beginning of every new conversation. - Switching to a different project context. - After a long break in the same session. ## Procedure ### Step 0: First-time onboarding check Before any other initialization, check whether this vault has been onboarded. ```bash test -f "$SYMBIOSIS_BRAIN_VAULT/.sb-initialized" && echo present || echo absent ``` - If `present` → continue to Step 1 (normal bootstrap, welcome was done previously). - If `absent` → invoke skill `brain-welcome`. After it returns, the marker exists; continue to Step 1. This step runs at most once per vault (welcome-skill writes the marker on success). If welcome-skill fails before writing the marker, the next session retries. ### Step 1: Verify MCP server Call `brain_status`. If it returns an error: - Inform the user: "Symbiosis Brain MCP unavailable, falling back to MEMORY.md". - Read MEMORY.md for basic context. - Skip Steps 3-5 — those require MCP. - Continue without MCP tools for this session. ### Step 2: Load critical facts (L0) Call `brain_read("CRITICAL_FACTS.md")`. ~120 tokens. Never skip. ### Step 3: Detect & validate scope Use `brain-cli scope-resolve` to compute the canonical scope. Path to the tools repo comes from `$SYMBIOSIS_BRAIN_TOOLS` (exported by SessionStart hook). **On Windows** — PowerShell first (bash subshell launched by Claude Code often lacks `uv` on PATH, see [[mistakes/uv-not-on-bash-path-windows]] if recurring