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.

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/.reasonix, or the repo's scripts/ directory.

Hold the result as JEV_RESULT. Shape (stable — see design reference for full schema):

available, jev_called, matched, fallback, fallback_reason, agent, agent_source, skill, pipeline, attach, complexity, confidence, match_type, reasoning, stack, signals, signal_scores, domain_scores, source, latency_ms, usage, agents, gate_score, fits_scores, stage1_shortlist, pre_route_hint, and intent_alignment (the hook-generated baseline alignment receipt).

attach is the list of extra skills that ride with skill (for example programming for Go work, testing when tests are part of the work). The script already validated every name; it is the whole Phase 4 stack.

latency_ms and usage are itemized dicts ({"stage1_ms","stage2_ms","total_ms"} and {"stage1","stage2"}). Read .total_ms for a single latency figure.

Gate: fallback == true → Phase 1F. Every matched result, including source == "jev-trivial-bypass", proceeds to Phase 2: ALIGN INTENT.

Phase 1T: TRIVIAL-BYPASS (source == "jev-trivial-bypass")

Stage 1's gate fired: gate_score below threshold, no agent/skill/pipeline is needed. It remains a direct-handling path, but it must still pass through Phase 2 so the user outcome is restated and Jev validates it. After an aligned Phase 2 result, show Classification: Trivial and Source: jev-trivial-bypass, then answer or do the one-line action directly. Do not run Phases 3–5 or call build-dispatch.py. Stop there.

Phase 1F: UNAVAILABLE (fallback == true)

Jev could not classify this request. JEV_RESULT.source explains why:

• unavailable — neither configured Jev transport is available. /d accepts Vercel AI Gateway (AI_GATEWAY_API_KEY) or the direct Jev API (TYPESAFE_API_KEY), selected by JEV_TRANSPORT=auto|vercel|direct.
• invalid-pick — Jev's pick was not a valid manifest name.
• error — a Jev call timed out or failed.

Show:

===================================================================
 /d: Jev unavailable — [JEV_RESULT.fallback_reason]
 Use /do for manifest-based routing.
===================================================================

Fail open to /do's full routing flow and continue the request. Do not reject the request merely because Vercel AI Gateway is unavailable.

Phase 2: ALIGN INTENT (required for every matched /d route)

MANDATORY STOP: For every matched /d invocation, write PROPOSED_INTENT and run the validator on that exact text before any routing banner, dispatch, answer, edit, or other action. JEV_RESULT.intent_alignment is only the hook baseline and does not satisfy Phase 2. This requirement has no exception for force routes, trivial routes, or an apparently aligned baseline.

Before selecting the work method, write PROPOSED_INTENT: a concise one- or two-sentence restatement of what the user wants accomplished. State the outcome and each deliverable the request names or directly requires. Copy every explicit constraint in the user's words: limits ("only", "at most"), exclusions ("don't touch", "do not deploy"), required methods, and authorization boundaries. Do not add deliverables the user did not ask for, such as extra tests, docs, cleanup, refactors, or verification steps. Do not add notes about missing inputs or preconditions; the validator decides whether clarification is needed. Do not describe the selected agent, skill, or implementation mechanics as the outcome. Preserve the user's words where precision matters.

Run the Jev validator even when the hook already supplied JEV_RESULT.intent_alignment; that receipt validates a conservative baseline, while this call validates the actual restatement that will enter the task spec. Put the request, route JSON, and proposed intent in temporary files rather than shell-splicing user text, then call:

python3 "$SDIR/jev-intent-align.py" \
  --request-file "$REQUEST_FILE" \
  --route-file "$ROUTE_FILE" \
  --proposed-intent-file "$INTENT_FILE" \
  --json-compact

The validator sends one bounded state and all independent questions together through the selected Jev transport. It checks whether the outcome and constraints are preserved, the route can cover the material scope, the restatement is too narrow, it introduces unrequested work, and essential clarification is needed. It returns aligned, clarification_needed, issues, and raw scores.

Show this before the routing banner:

Intent alignment (/d):
  -> Restated outcome: [PROPOSED_INTENT]
  -> Jev: [aligned|review|unavailable] [issues, if any]

Gate:

• clarification_needed == true → ask one concise question that names the essential ambiguity; do not dispatch until answered.
• alignment == aligned and source == jev-trivial-bypass → direct handling in Phase 1T; otherwise → Phase 3.
• alignment == review because scope is lost, work was added, or the route cannot cover the request → correct PROPOSED_INTENT or the route and run this validator once more. Carry unresolved issues into task_spec.gaps; do not silently proceed as though Jev approved it.
• alignment == unavailable or error → state that validation was unavailable, preserve the verbatim request and proposed intent in the task spec, then continue under the normal /d routing result. Gateway outage must not become a false request rejection.

This runtime gate applies to every matched route, including force-routes and trivial bypasses. A Phase 1 fallback cannot run this gate because no usable Jev route exists; it fails open to /do as described in Phase 1F.

This is an instruction gate enforced by the /d contract, not a hook-enforced technical boundary. The user remains the final backstop if an agent violates it.