USE CASE / Choice

Model routing

Choose code, a light model, a reasoning model, or a person

A representative input (state)

Task, available models, and resource limits

Question type

Choice

Question instruction

Choose code, a light model, a reasoning model, or a person

When below threshold

Code checks budget, access, and availability before routing

Make model routing comparable

Code first excludes unavailable, unauthorized, or over-budget handlers. Choice can propose a route among the rest. Length alone is a poor complexity proxy; label examples for new text, multi-step reasoning, and deterministic calculation separately.

Three edge cases to test

2+2: deterministic code
Long but simple formatting: length alone does not require reasoning
Account access: permission check precedes routing

Example request

This is a design draft, not an actual Jev answer or accuracy test.

{
  "state": "Summarize this page and cite the source.",
  "model": "jev-latest",
  "questions": {
    "decision": {
      "type": "choice",
      "instructions": "Which handler should receive this task?",
      "criteria": {
        "code": "A deterministic rule can fully solve it",
        "light_model": "A narrow text task with low uncertainty",
        "reasoning_model": "Requires multi-step reasoning or new text",
        "human": "Needs human judgment or approval"
      }
    }
  }
}

Limits and fallback

Message length alone is a poor complexity signal; keep a fallback model.

What does the support team actually need to decide?

Follow one support ticket from raw text and verified facts through three questions, an illustrative answer, edge cases, and launch evaluation.

Worked example: design a Jev workflow for a missing delivery