Decision Models
Feature
A feature tracking decision models ("System One") — models that return a judgment rather than text. Family tree, pricing, calibration, threshold design and adoption criteria, from primary sources. They differ from generative LLMs in billing unit and evaluation, so they are kept as a separate feature here.Feature · Last updated October 18, 2026
A decision model (System One) generates no text. It takes a state plus typed questions and returns only a probability distribution over the answers you defined, in a single forward pass. That makes it fast, cheap and structurally impossible to return a malformed option. But type safety is not correctness: calibration and threshold design decide whether it works in production. TypeSafe's Jev is the reference point, and more than a dozen open implementations appeared from mid-September 2026.
1. What changed
Ask an LLM which team owns a ticket and you pay for a paragraph, then parse it back into an if statement — slow, billed on output tokens you discard, and breakable. A decision model drops generation entirely: it takes state and typed questions and returns a distribution over exactly the answers you allowed. The schema is the output space, so no invented option can come back.
There are three primitives. choice (unordered selection: routing, intent, tool choice), score (ordered scale: urgency, intensity, risk) and noul (a yes/no probability: phishing, jailbreak, refund request). Options arrive with the request, so unlike a classic classifier there is nothing to train.
2. The reference point: Jev (TypeSafe AI)
| Item | Detail |
|---|---|
| Current version | jev-1.14.0 (Oct 14, 2026, jev-preview). The SDK default jev-latest still points to jev-1.13.0 in the official docs as of Oct 16 (a switch is due a week after release). See "3. Jev 1.14.0" below |
| Vendor | TypeSafe AI (San Francisco). Co-founder Diogo Almeida came from Google Brain and OpenAI and is a co-author of the InstructGPT paper and the GPT-4 technical report. Early access on Sep 15, 2026, alongside a $40M seed round led by DCVC |
| Form | Closed managed API. POST /v1/systemone, Python / JavaScript SDKs |
| Price | $0.042 per million input tokens; output is free |
| Latency | 70–500 ms per call. Effectively flat in the number of questions and options (76 ms for 2 options, 75.5 ms for 200) and linear only in state length (~59 ms plus ~5.5 ms per 1k tokens) |
| Limits | Up to 255 options per choice; 64k tokens per request (state plus longest question must fit in 32k) |
| Training | RLCD (Reinforcement Learning for Calibrated Decisions). TypeSafe describes it as a target — agreement between stated probability and observed outcome — not an algorithm name |
| Disclosure | Architecture, parameter count and training data are undisclosed. Black-box reconstruction points to a pretrained causal transformer whose serving and readout layers were rebuilt for the decision interface |
The most important third-party evaluation comes from a University of Bonn, Lamarr Institute and Fraunhofer IAIS group, which ran jev-1.13.0 zero-shot across 37 datasets and 346,009 requests for under $10 of API spend, with Qwen3.8-27B and Gemma-4-E4B scored on identical requests. Jev beat Qwen3.8-27B on 27 of 37 datasets, reached 95–99% on IMDB, SST-2, HellaSwag and ARC, and 86.7% on Belebele across 122 languages. Its choice probabilities were well calibrated and supported selective prediction. One caveat: binary noul probabilities rank well but sit poorly against a fixed 0.5 threshold, so a hardcoded cutoff is the wrong way to read them.
The vendor also publishes its weak spots: multi-step maths and planning (System Two work), counting, date comparison and literal reading. TypeSafe's own "jaggedness" page lists maths, counting and date comparison, and the weakest reported category was trading bots.
3. Jev 1.14.0 (Oct 14, 2026)
TypeSafe AI released Jev 1.14.0 on Oct 14, 2026 under the jev-preview alias. It is a set of small, steady improvements across the board, with the largest expected gain in multilingual support. Pricing is unchanged at $0.042 per million input tokens, with output free.
| Item | Detail |
|---|---|
| Images (experimental) | Enabled with the header TypeSafe-Danger-Zone-Images: true. Images are listed once in an assets map and referenced from state, instructions or criteria. TypeSafe notes 1.13.0 was multimodal all along. PNG/JPEG only, up to 16 MiB per file, 256–1568 px per side, 32 MiB per request; billed as normal input tokens |
New box type | Returns one bounding box per question as normalised top/bottom/left/right fractions in 0–1, plus a confidence score. Requires 1.14.0. It always returns a box even when the object is absent, so TypeSafe recommends pairing it with a Noul question that checks existence |
| Long context (experimental) | Default is 64k tokens per request and 32k per question; the header TypeSafe-Danger-Zone-Long-Context: true raises both to 262k. Reliability drops, so short contexts remain the recommendation |
| Rollout | jev-preview is 1.14.0 now; jev-latest switches in a week; jev-1.13.0 stays available with 60 days' notice before deprecation; 1.14.0 gets 30 days' notice |
| Caveat | TypeSafe states plainly that none of the three features is ready for production (the "danger zone"). Images perform worse than text, and the simplest possible decompositions help most |
| Benchmarks | While stating it dislikes public benchmarks ("antibenchmaxxing"), TypeSafe published internal intelligence charts this time. It notes the measurement compares only open-weight models, is likely biased toward its own models, and should not be expected to stay consistentVendor-reported |
In a small box test on 36 painting crops, each cutting off part of the target, four per-edge Noul questions caught 30 of 36 cut-offs; a single "is all of it inside" question caught 26, and drawing the box as an outline and asking about it caught 20.Vendor-reported
AIfrontier view Box is a first step from judging to locating. It keeps the typed-output philosophy while reaching toward inspection and localisation tasks. But "always returns a box" is a different trap from type safety in decisions — always pair it with an existence question. Related: Local and cloud LLMs — latest
4. The lineage map (as of Oct 16, 2026)
Within a week of Jev, open projects reimplemented the same interface. They split three ways: bidirectional encoders (no KV cache — fastest on CPU), causal decoders with LoRA adapters (long state, more world knowledge), and extraction-only approaches that read logits from existing models.
| Model | Origin / licence | Architecture | Speed and price | Caveats |
|---|---|---|---|---|
| Jev | TypeSafe AI / closed | Undisclosed | 70–500 ms; $0.042/M input, output free | The confidence ordering open models have not matched. Validate thresholds yourself |
| Laya | Convai Innovations (Nandakishor M) / Apache 2.0 | ModernBERT-large 421M (English) plus mmBERT 322M (100+ languages), decision head | 39.5 ms per question, 32.8 ms multilingual on a Tesla T4; 7.2 ms batched over ten | Base checkpoints are near chance (0.362/0.342 against a 0.461 majority baseline); the headline 0.766 is the fine-tuned typed-decisions checkpoint. Accuracy drops past ~20 options; 512-token default context |
| Von | Open (Sep 23, 2026) / 395M | Bidirectional encoder, no cache | Under 15 ms on CPU | Less context and world knowledge than causal-decoder models |
| Kev 1.0 | Jared Palmer / Apache 2.0 | Qwen3.5 / 3.8 bases (0.8B, 4B, 9B, 27B); drop-in compatible with the TypeSafe SDK, temperature-calibrated | Kev-4B: 18.1 ms on an H100, 5 questions in 721 ms on an Apple M5. Kev-27B needs an 80GB-class GPU. Fine-tuning Kev-4B starts around $1 of H100 time | Slightly below Jev 1.14 on the author's held-out index; Jev is stronger on MMLU-Pro-style knowledge. On AIMultiple's browser tasks, Kev-27B scored 40/50 vs Jev 17/50 |
| Jeff v1.3 / Jeff-Code | firelex / code MIT, weights Apache 2.0 (some adapters non-commercial) | Qwen3.5-0.8B base. v1.3 is built around 15 task adapters and ships GGUF (v1.2 remains available under its old name) | ~22–30 ms | Placed in front of Qwen3.8-27B, Jeff-Code cut wall time by 32% (47% faster) across 1,242 tasks on six benchmarks, with pass rate 62.4% vs 62.8%Vendor-reported |
| SemIf | TheoLeeCJ / MIT | Reads logits directly from existing models — no custom head | 5.21× faster than compact JSON generation; 20.03 decisions/second with 4-bit Qwen3.5-4B | 0.813 on its author's benchmark. Research and experimentation |
| NanoJev | TianyuCodings / MIT | Qwen3-0.6B with parallel decision heads | — | Published results are ViZDoom game-control only; CUDA required; research use |
| jevlike | vinnylarouge / MIT | Byte embeddings | About 100× faster than a small decoder | The author calls it a research starter — not for production |
| Perplexity Decider v1.1 27B | Perplexity / Apache 2.0 (open weights) | 27B, non-causal attention, multimodal; ~49 GiB of weights | $0.02 (half of v1) | Cheapest on the AA Decision Index at $17 per million tasks. Perplexity claims it edges Jev on its own Decision Index 0.3 |
| Clef / Clef-flash / Clef-omni | Cloudflare / Apache 2.0 | Clef: frozen Qwen3.8-27B plus LoRA. Clef-flash: Qwen3.5-9B. Clef-omni: Qwen3-Omni-30B-A3B (audio and video) | Clef $0.24 (64k); Clef-flash $0.038 (cut from $0.09 on Oct 9; hosted context now 24k); Clef-omni $0.15, ~130 ms on text | Jev-API compatible. Clef-flash traded hosted context (64k to 24k) for the price cut; the weights support 256k |
| d1 / d1-ultra / d1-3B | Liquid AI / hosted closed, d1-3B open | d1-ultra builds on a larger open-weight base with heavy custom changes; text and images | d1 $0.02; d1-ultra $0.042 (Oct 15); d1-3B 8 ms on an RTX 4090 | Liquid claims d1-ultra beats Jev 1.14 across 112 evaluations and leads other decision models on the AA Decision Index by 8+ pointsVendor-reported |
| Microsoft-Decision-1 | Microsoft / via Foundry | Reported as Qwen3.5-9B based | About $31 per million tasks on the AA Decision Index (on its Pareto frontier) | Scores 54. Its 40% non-hallucination rate (choosing "I don't know") leads all decision models |
| OpenAI Decisions API | OpenAI / closed (beta) | Reported as GPT-6 Luna based | $0.10 (reported) | Announced at DevDay on Oct 6; little primary detail so far |
Watch the naming collision. Laya is called "the open-source Jev", but most of its headline numbers come from a checkpoint fine-tuned on the benchmark's own training split, not from the base weights. And the Jev column in the Laya comparison table is drawn from third-party publications — the Laya author states he had no access to the TypeSafe API. Always read a number together with its conditions: checkpoint, routing, context length and option count.
5. Independent benchmarks: Artificial Analysis and AIMultiple
October brought the first results measured by someone other than the vendors on a shared yardstick. The Artificial Analysis Decision Index v1.0 weights four evaluations equally: knowledge and hallucination (AA-Omniscience-Decision), reasoning (HLE-MultiChoice), tool calling (When2Call) and classification (WildGuardTest). Source: Artificial Analysis
| Angle | Result |
|---|---|
| Overall | Jev 1.13 leads at 58; GLiDE and Microsoft-Decision-1 on 54 |
| Cost per 1M tasks | Decider v1.1 27B cheapest at $17; Microsoft-Decision-1 ($31) and Jev 1.13 ($42) also on the Pareto frontier; GLiDE $119 |
| Median time per task | Celeris-1 Decision fastest at 0.06 s; Jev 1.13 at 0.13 s |
| Calibration | Every decision model is overconfident, mostly on knowledge and reasoning; tool calling and classification are relatively well calibrated |
| Saying "I don't know" | Microsoft-Decision-1 leads the non-hallucination rate at 40%, then Jev 1.13 at 35% and Mercury Decide at 32%; no other model reaches 17% |
| Versus LLMs | Claude Haiku 5.5 (Low) scores 61, above Jev, but takes 1.4 s per task (~11×) at ~4.4× the cost |
AIMultiple evaluated 50 decision models and put Jev 1.13 first on classification. On browser tasks, though, Jev frequently returned "blocked": Kev-27B completed 40 of 50 against Jev's 17. Source: AIMultiple
AIfrontier view Most "beats Jev" claims — d1-ultra's, Decider v1.1's — rest on the vendor's own metrics. On independent scoring Jev still leads overall, yet Decider wins on cost, Celeris on speed and Microsoft on knowing when not to answer. Pick the axis that matters for your workload rather than a single composite.
6. Calibration and threshold design
The value of a decision model is not speed; it is a confidence you can put in an if statement. If the model says 0.95 about things that happen 70% of the time, every threshold you set is wrong. That agreement between stated probability and observed frequency is calibration — a property of groups of predictions, not of one answer. The standard summary statistic is ECE (expected calibration error), where zero is perfect.
Laya publishes an ECE of 0.081 against Jev's 0.246, but that is the routed measurement — and Laya's own model card warns that shipped probabilities are overconfident and should be recalibrated on held-out data before they drive consequential actions.
In practice, split confidence three ways: act automatically on high confidence, route medium confidence to a stronger model or a human, hand low confidence to a human. Laya's Act/Escalate head is trained with a cost matrix (+1 correct, −3 wrong, −0.5 escalate), so automatic action only beats escalation above 62.5% accuracy. Temperature scaling reshapes a distribution but cannot repair a ranking that is already wrong — the one property where the open models still trail Jev.
7. Adoption checklist (10 items)
- Does the judgement reduce to a finite set of answers? If you need free text, that is LLM work
- Are exact requirements — permissions, price ceilings, balances — enforced in code, not by the model?
- How many options? Above 20, prefer Jev / Kev / causal-decoder models; at 20 or below, Laya or Von
- How long is the state? Does 512 tokens suffice, or do you need 8k–64k?
- Did you fit a temperature on your own labelled data, bound to the exact weights, precision, runtime and prompt version?
- Is the threshold set per question, scaled to the cost of being wrong?
- Can the data leave your environment? If not, self-host Laya, Von or Kev
- Is the latency budget a frame, or a network round trip?
- Did you check that shuffling the option order moves the probabilities? (Shuffle when you calibrate)
- Did you benchmark a small LLM with structured output and plain deterministic rules on the same task? Simpler methods sometimes win
8. Sources
- Artificial Analysis: Introducing the Artificial Analysis Decision Index (Oct 2026)
- AIMultiple: Decision models (Oct 2026)
- Liquid AI: d1-ultra (Oct 15, 2026)
- Cloudflare: Clef-omni takes audio, video, image, and text input (Oct 9, 2026)
- Microsoft: Microsoft-Decision-1 (Oct 2026)
- Hugging Face: perplexity-ai/pplx-decider-v1.1-27b
- GitHub: jaredpalmer/kev / firelex/jeff
- Forbes: Decisions, Decisions (Oct 12, 2026)
- TypeSafe AI: Models (what jev-latest points to)
- TypeSafe AI: Introducing System One Models and Jev (Sep 15, 2026)
- Runware: Jev, Laya and the emerging role of decision models (Sep 28, 2026)
- Jev vs Laya: Comparing and Choosing Between Closed and Open Decision Models (Sep 23, 2026)
- Jev and the seven open clones: a model that never writes a token (Oct 6, 2026)
- Layer3Labs: The Decision Models You Can Use Today (Oct 2026)
- Hacker News: Jeff – Jev-compatible 0.8B decision models, trained at home (Sep 28, 2026)
This page organizes public information. Jev's internals, and many of the open implementations' figures, are vendor-reported and have not been independently reproduced by us. Read every number together with its conditions.