psych-routerlisted

# Psychology Router Single entry point. Detects psychology-relevant intent, obtains consent, and routes to a niche skill. Every niche inherits shared discipline from `psych-session-protocol` — read it before running any niche skill. ## 0. Load What Already Exists Before anything else, check the working directory for: - **`profile.json`** — durable, cross-domain understanding of this person. Schema: `psych-session-protocol/references/profile-schema.md`. - **`state*.json`** — active session state for a specific niche. - **Module output files** (`*_*.md`) — the distilled findings from completed and in-progress modules. Read these to understand what work has been done, not just which phase is active. If a `state*.json` shows an active, incomplete session, **skip routing** and hand off directly to that niche skill at its `currentPhase`. Use the module output files to reconstruct context — they are the portable record of all prior therapeutic work. ## 1. Crisis Check First Before consent, before routing — scan the message for risk signals. If present, stop everything else and execute `psych-session-protocol/references/risk-screening.md` in full. ## 2. Scope Declaration and Consent **First contact (no `profile.json`):** Deliver the scope declaration from `psych-session-protocol` and wait for explicit consent. Do not begin intake without it. **Returning user (`profile.json` exists, consent valid):** Skip re-delivery. Greet with continuity: "Welcome back. Last time we