1. Data source
  2. Decision schema
  3. Model inference
  4. Structured result
2 Decision schema 3 typed questions
  • prioritychoicerun_firstrun_laterskip
  • relevancescorelowmediumhigh
  • covers_diffnoulprobability 0–1

3 Model inference typesafe/jev-1.13

Waiting for a run.

4 Structured result

Run the demo to see the JSON answers, the highlighted pick and the final action.

Call Jev yourselfSame data and schema, straight to Flatkey. Set FLATKEY_API_KEY and run.
curl -sS https://router.flatkey.ai/api/alpha/decisions \
  -H "Authorization: Bearer $FLATKEY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "typesafe/jev-1.13",
  "state": "PR #4821 — auth session refresh\nChanged files:\n  src/auth/session.ts (refresh token rotation, revoke on reuse)\n  src/auth/middleware.ts (attach refreshed cookie)\n  tests/auth/session_refresh.test.ts (updated)\nNot touched: checkout, billing, search.\n\nCandidate test:\n  name: tests/e2e/checkout_flow.spec.ts\n  description: Full browser checkout from cart → payment → receipt\n  avg_duration: 4m12s\n  tags: e2e, checkout, stripe\n\nTask: priority (run_first / run_later / skip), relevance, covers_diff.",
  "questions": {
    "priority": {
      "type": "choice",
      "instructions": "Given this diff and this candidate test, how should CI schedule it? Prefer run_first when the test clearly covers changed behavior; skip when it is unrelated; use run_later when it is weakly related or only a smoke check.",
      "criteria": {
        "run_first": "The test exercises the changed modules, APIs, or failure modes—run it in the first wave before merge-critical gates",
        "run_later": "Weak or indirect overlap, or a broad smoke/e2e that can wait until the targeted wave passes",
        "skip": "No meaningful overlap with the diff; spending minutes here wastes the budget"
      }
    },
    "relevance": {
      "type": "score",
      "instructions": "How strongly does this test protect the changed behavior, based only on the paths and test name/description provided.",
      "criteria": [
        "low",
        "medium",
        "high"
      ]
    },
    "covers_diff": {
      "type": "noul",
      "instructions": "This test would exercise at least one changed file, symbol, or user-visible path described in the diff—true only when there is concrete overlap, not a vague suite membership."
    }
  }
}'

No Flatkey key yet? Get one for Jev 1.13 →

Run with real Jev

Sign in and connect a key

  1. Sign in with Google.
  2. Connect your Flatkey or OpenRouter key on the next screen. Get a Flatkey key for Jev 1.13.
  3. Come straight back here and press Run again.

This site is for researching, sharing and cataloguing Jev use cases. Your key is only there to make trying Jev convenient: it is stored encrypted, used only for runs you trigger, never used for anything else, and you can delete it anytime.

About this use case

Use Jev for test selection: incoming state, Jev decision, routed outcome

Who / when

Audience

  • CI owners who cannot afford full suites on every push
  • harness builders handing the model an option list, not a blank plan
  • teams that want cheap relevance scoring before expensive test minutes

Triggers

  • a PR changes a few files and you need a ranked subset of tests
  • full suite cost or wall time is the bottleneck, not inventing new tests
  • the harness already has the test catalog, thresholds, and budget
  • you want calibrated run_first / defer / skip instead of an LLM rewriting the plan

The workflow

  1. 01
    Diff + candidateChanged files and one testInput
  2. 02
    Priorityrun_first / run_later / skipJev
  3. 03
    RelevanceScore + covers_diff flagJev
  4. 04
    Code gateQueue, defer, or dropYour code

Question shape

{
  "priority": {
    "type": "choice",
    "instructions": "Given this diff and this candidate test, how should CI schedule it? Prefer run_first when the test clearly covers changed behavior; skip when it is unrelated; use run_later when it is weakly related or only a smoke check.",
    "criteria": {
      "run_first": "The test exercises the changed modules, APIs, or failure modes—run it in the first wave before merge-critical gates",
      "run_later": "Weak or indirect overlap, or a broad smoke/e2e that can wait until the targeted wave passes",
      "skip": "No meaningful overlap with the diff; spending minutes here wastes the budget"
    }
  },
  "relevance": {
    "type": "score",
    "instructions": "How strongly does this test protect the changed behavior, based only on the paths and test name/description provided.",
    "criteria": [
      "low",
      "medium",
      "high"
    ]
  },
  "covers_diff": {
    "type": "noul",
    "instructions": "This test would exercise at least one changed file, symbol, or user-visible path described in the diff—true only when there is concrete overlap, not a vague suite membership."
  }
}

Gate policy

≥ 0.90

Honor priority: enqueue run_first immediately; schedule run_later after the first wave; never spend budget on skip when covers_diff is false.

0.65–0.90

Prefer run_later over run_first; log probabilities and widen the first wave only if the budget allows.

< 0.65

Do not auto-promote to run_first; treat as skip or human review of the selection policy.

Failure modes

Pre-launch checks before you trust auto-routing:

  • Promoting unrelated e2e suites to run_first because the name sounds important;
  • Skipping a unit test that imports a changed module because the path string did not match literally;
  • Asking a chat model to rewrite the whole verification plan instead of scoring a fixed catalog;
  • Letting Jev invent new tests or authorize merge—selection only, enforcement stays in CI;
  • Ignoring duration budgets and scheduling every high-name test first;
Keep exact work in code: the test catalog, path overlap indexes, duration budgets, flake quarantine lists, and the final enqueue or skip stay deterministic. Use Jev only for the meaning-level gate—run_first, run_later, or skip—then let your thresholds spend the CI budget.

FAQ

How is this different from coverage-based test selection?

Coverage and import graphs give hard overlaps; they miss renamed symbols, shared fixtures, and "this e2e would catch the auth cookie bug" judgment. Jev answers run_first / run_later / skip with calibrated scores you can threshold on top of those exact indexes.

Should Jev invent which tests exist?

No. The harness owns the option list, permissions, and budget. Jev only chooses among candidates it was handed—same pattern as routing notes or tools.

What does the Flatkey call look like?

POST https://router.flatkey.ai/api/alpha/decisions with Authorization: Bearer …, Content-Type: application/json, and a body of state, model (typesafe/jev-1.13), and questions (choice / score / noul). This is not an OpenAI-compatible /v1 chat endpoint.

Can I bring my own API key?

Yes. Try the free demo above without signing in. To run it live on your own text, sign in with Google and connect a Flatkey or OpenRouter key (a quick test call runs when you save it). Manage or delete it anytime under Dashboard → BYOK. Keys are stored encrypted on the server, used only for runs you trigger, and never sent back to the browser. Need a Flatkey key? Get one for Jev 1.13 on Flatkey.

Is this the official TypeSafe Jev product page?

No. jev-llm.com is an independent research and practice site. Verify pricing, models and terms at the original TypeSafe sources.

Sources

Seen on X
Independent-site note: jev-llm.com is an independent research and practice site. It is not the TypeSafe AI official site. Verify models, pricing and terms at the original source.