reference-router

# reference-router Native entry point into the `fable5-workflows/` reference corpus. Obey progressive disclosure; never context-dump. ## Load order 1. Read `manifest.json` (corpus root) — the machine inventory: every file's `path`, `tier`, `scope`, `tags`, `runtime_affinity`, `inject`, `size_bytes`, `sha256`, `anchors`. This ONE file tells you what exists and where, without opening any content file. 2. Pick file(s) whose `scope`/`tags` match the question and whose `inject` != `exclude`. 3. For a large file (`tier: deep-dive-analysis` or `L1-card`), use its `anchors` (id -> line range) and `Read` offset/limit to pull only the slice — not the whole file. 4. Honor `inject`: `inject` = safe to load; `reference-only` = specific sections only; `exclude` = do not auto-load (raw L0 / `_verbatim/`), pull a slice only via a direct pointer. ## Runtime affinity - `claude-specific` — Claude Code CLI mechanics & Dynamic-Workflow source; load only for Claude. - `portable` — delegation/orchestration knowledge; any runtime's analysis agent may use. - `mixed` — per-anchor `affinity` disambiguates. Non-Claude consumers: `_meta/RUNTIME-AFFINITY.md`. ## Do not - Do NOT load whole catalogs or `_verbatim/*.js` (Claude Dynamic-Workflow source, `exclude`). - Do NOT trust prose sizes in any `INDEX.md` — `manifest.json` is authoritative for size/sha. Human routing still works via each directory's `README.md` -> `BROWSE.md`.