d

# /d — Jev Router Classifies requests through Jev and dispatches to the matched agent, skill, and pipeline. Before every dispatch, it restates the requested outcome and uses Jev to check that the restatement and route preserve it. The classification path has four layers: a deterministic `pre-route.py` force-route guard (offline, runs first, authoritative for git/security only), a configured Jev transport presence check, a two-stage classification (a cheap wide-rank stage 1 over all manifest candidates plus a trivial-bypass gate, then a full-detail shortlist-rerank stage 2 with per-candidate fit checks, stack/fan-out signals, and domain-attachment checks), and a deterministic attachment step that lists the extra skills to load. Design rationale: `${CLAUDE_SKILL_DIR}/references/jev-classifier-design.md`. ### Phase Banners Every phase: `/d > Phase N: PHASE_NAME — description...` After intent alignment resolves: `===` routing banner. Both required. --- ### Phase 1: CLASSIFY `scripts/jev-route.py` owns the entire classification in one subprocess call. When `JEV_RESULT` is already in context (the `jev-route-injector` hook ran the script before your first token), use it and skip the command below. ```bash REQUEST_FILE=$(mktemp); printf '%s' "{user_request}" > "$REQUEST_FILE" python3 "$SDIR/jev-route.py" --request-file "$REQUEST_FILE" --json-compact rm -f "$REQUEST_FILE" ``` Resolve `$SDIR`: `${HOME}/.claude/scripts`, falling back through `.hermes`/`.factory`/`.codex`/`.re...