routelisted

# Route Stage Analyze an enriched note against routing memory, vault rules, and generic signals. Move to destination or mark for review. See `references/pipeline.md` for stage definitions and status flow. See `references/routing.md` for the scoring algorithm. See `references/para.md` and `references/johnny-decimal.md` for the two folder systems a vault may use (often both, mid-migration). See `references/routing-memory.md` for the correction and learning loop. ## Input An enriched note in the inbox with `status: enriched`. ## Process 1. Load routing context: - Read `.routing-memory.md` from vault root (create with defaults if missing) - Read vault CLAUDE.md for disambiguation rules - Run `sb vault structure` for available destinations - Run `sb note context --note "{note-path}"` for keywords and signals 2. Score destinations (priority order): a. Check `.routing-memory.md` corrections for matching topics/keywords b. Check `.routing-memory.md` learned patterns c. Apply vault CLAUDE.md disambiguation rules d. Apply generic signal scoring (per `references/routing.md`) Each destination from `sb vault structure` carries a `type`. For Johnny Decimal destinations (`type: 'jd'`) also use `area` and `code` when scoring: match the note's topic to the `area`, and prefer an ID `code` (e.g. `67.01`) for a specific note or its parent category `code` (e.g. `67`) for a loose note. See `references/johnny-decimal.md`. 3. Apply threshold: - Score >= `auto-r