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/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`) 3. Apply threshold: - Score >= `auto-route-threshold`: auto-route, move file, set `status: routed` - Score < threshold: set `status: pending-review`, return without moving 4. If auto-routing, move the file: ```bash npx @techpickles/sb note move --from "{note-path}" --to "{destination}/" ``` Update frontmatter: `status: routed` 5. If pending-review, present suggestions to human (when called by orchestrator): - Show top 2-3 destinations with scores and reasoning - Include "Leave in inbox" o