# Jev and System One Models (Resonance) > Diogo Almeida / TypeSafe AI, announced 2026-09-15. A hosted model that generates no text: state and typed questions in; a Choice, a Score, or a Noul (yes/no) out, each with a calibrated probability, in one parallel pass. Evaluated six days after launch from the vendor's post, one walkthrough, and five independent benchmarks. Not used hands-on. The resonance is real and narrow: Jev is a typed decision layer that fits under ODD's procedure tier. It is not an epistemic OS. Type-safe is not true; a valid label can be a wrong label. Companion guide: [Jev in the ODD Stack](https://klappy.dev/page/docs/guides/jev-in-the-odd-stack). --- ## How This Was Found Not a studied work. The launch turned the AI world upside down over one week; the operator sat it out, then came back through Nate B. Jones, the operator's go-to YouTuber for AI news, and his walkthrough and asked whether it fits a design already dictated on a Saturday run: boarding by progressive disclosure, prompt caching, and a bootloader that classifies what is worth seeing before anything is written. It did — with edges. A Grok research seed and five independent benchmarks were folded in and audited. Four of the seed's six cited repos do not exist; the benchmarks do. --- ## ODD Principle: The Verdict and the Evidence Are Different Artifacts A decision is cheap to emit and expensive to justify. ODD keeps the two apart: procedure may emit verdicts at any speed, but a verdict becomes a claim only when inspectable evidence comes with it. Confidence, however well calibrated, is a property of the emitter. Evidence is a property of the world. --- ## Convergent Quotes (Non-Authoritative) > "unstructured state in, typed probabilistic decisions out" > — Diogo Almeida, *Introducing System One Models & Jev*, TypeSafe (2026) > "Only jev bluffs." > — nibzard, *decision-model-benchmark* README (2026) > "it only pays if you test it against the LLM call it replaces" > — Nate B. Jones, walkthrough description (2026) --- ## Where ODD Aligns - **The answer space is fixed before the call.** Jev returns only what the schema declared. `oddkit_gate` and `oddkit_encode` already refuse to let the emitter invent a category at runtime. - **Uncertainty is an output, and low confidence escalates.** Threshold-and-hand-off is the creed's last line as a routing rule: what has not been verified is not implied. - **Many narrow questions beat one big one.** The vendor reports it; the phishing benchmark measured it (62.6% asked once, 95.0% decomposed). ODD's gate already evaluates each prerequisite independently. - **The surrounding code constrains the model.** Smart if-statements inside ordinary software is skills-as-procedure with a better classifier. - **Attention is the scarce resource.** Jev decides which questions are worth asking — which email earns a draft, which docs earn a read. That is the bottleneck rule applied to operator attention. - **The vendor publishes its debts.** Every headline result carries a nuance block: in-house workflows, reference answers from two labs, possibly subsidized pricing. A claim with its debts attached. --- ## Where ODD Diverges (Explicit) - **A probability is not a receipt.** Jev returns no rationale, by construction. Audit gates must emit findings a reviewer can dispute. A 0.93 cannot be disputed, only trusted. - **"Cannot hallucinate" means "cannot leave the schema."** A confidently wrong `billing` is schema-valid. - **Agreement with bigger models is not observation of reality.** The vendor's 67.8% is agreement with a two-model panel on four vendor-authored workflows. Coverage restates it as accuracy. A panel of peers is not reality. - **It does not know that it does not know.** Off-distribution, calibration fails and the sign flips by output type; asked to apply a rule that lived in policy rather than in the text, it answered 44.7% right at 0.74 stated. On forced-uncertainty items every LLM admitted ignorance 97–100% of the time; Jev, 49.7%. - **It always answers.** Without an explicit "none of these," zero of thirty out-of-scope inputs were flagged. - **Chooser in the outer loop holds authority without a record.** The popular pattern puts Jev choosing next-step with LLMs demoted to tools. ODD puts the human gate and the mode declaration at that seat. A sequence of bare choices is a work unit with no receipt. - **A proprietary model is still a dependency.** Served by three hosts (TypeSafe, Vercel, Cloudflare Workers AI), so the substrate is swappable; the weights, the moving `jev-latest` alias, and the unproven price are not. ODD's procedure layer currently has zero inference dependencies. --- ## Why the Divergence Matters The risk is category drift. A fast, cheap, confident verdict machine is precisely the tool that tempts a team to automate judgment and call it governance. Jev sharpens ODD's procedure-versus-judgment line rather than moving it: it is a better procedure — a candidate upgrade wherever ODD classifies by keyword and stem today — and it is disqualified from judgment for the same reason a regex is. It cannot show its work. Hold that line and you get the cost collapse. Drop it and you get false confidence at 300 milliseconds. --- ## 5B Operationalization — Borrow the Decision, Build Only the Compiler **Borrow** — Choice / Score / Noul as the decision vocabulary, and the vendor's own arc: learn the job, then move steps to code. **Bend** — oddkit telemetry rows and disclosure flags become Jev `state` and `questions`; canon blockquotes become `criteria`, fetched live. **Break** — Jev standing in for challenge, gate, validate, or canon. Also break vendor calibration until measured on ODD's own vocabulary. **Beget** — The model. TypeSafe, an open port, SGLang `choices`, or a logit scorer over a small local model. Do not rebuild a decision model. **Build** — Only the lattice compiler: ontology → questions, telemetry → router state, compiled packs → candidate lines, code → effects. The smallest layer that makes a decision model trustworthy without pretending it is a mind. Bide verdict per https://klappy.dev/page/canon/constraints/borrow-evaluation-before-implementation: `waiting`. Two of three tripwires tripped during evaluation (access via Workers AI; independent reproduction). The remaining blocker is ours: a labelled gold set for one ODD seam. The guide says which seam and how. --- ## Confidence, Disconfirmers, Prior Art **Confidence.** Working belief, not established fact. The layer claim rests on five independent measurements days old plus the vendor's own architecture statement; none reproduced here; no hands-on use. Scope: bounded adopters with a private ontology. Nothing here is claimed for open-domain work. **What would retract it.** (a) Jev, or a successor, emits inspectable rationale alongside its probability — the "no receipt" divergence collapses and the gate/validate exclusion must be re-argued. (b) Abstention measured at LLM parity (>95% on forced-uncertainty) — the bluffing divergence collapses. (c) Off-distribution calibration measured near in-domain on ODD's own gold set — the "break vendor calibration" line is retired. (d) The bake-off shows the existing lexical classifiers already exceed ~90% — the borrow is not worth the dependency. **Strongest opposing view.** A calibrated probability *is* a kind of evidence, and demanding prose rationale from a classifier is asking a thermometer to explain itself; an audit log of inputs, questions, and outputs is inspectable enough. The page's answer: an audit log records the verdict, not the grounds; ODD's gates require grounds. Granting the opposing view still leaves Jev at layer 4. **Freshness and fairness.** The comparison target is Jev as documented by TypeSafe and Cloudflare on 2026-09-21, six days after launch, with a `jev-latest` alias that can move. Any line here may be stale by the time it is read; the tripwires in the guide say which ones. What Jev is solving that ODD is not: cost and latency of bounded decisions at product scale — a million verdicts for tens of dollars. What ODD is solving that Jev is not: whether the verdict can be trusted, disputed, and learned from. The two are not competitors; the page's only claim is about which layer each owns. **Prior art.** "Typed decision layer" is not a coinage; it is the vendor's own framing (System One) and the constrained-decoding lineage (SGLang `choices`, Outlines, XGrammar). "Lattice" as used in the companion guide is shorthand for beam-search-with-pruning over an ontology; if a better name exists it should be adopted. The procedure-versus-judgment line is ODD's, not new. --- ## Related Canon - [Jev in the ODD Stack](/docs/guides/jev-in-the-odd-stack.md) — the when-and-how guide, with the constraint table and tripwires - [Borrow, Bend, Break, Beget, Build](/canon/methods/borrow-bend-break-beget-build.md) - [Skills Are Procedure, Not Judgment](/canon/principles/skills-are-procedure-not-judgment.md) - [Audit Gates Are Spawned Agent Sessions](/canon/constraints/audit-gates-are-spawned-agent-sessions.md) - [Retrieval-Disclosure Contract](/canon/constraints/retrieval-disclosure-contract.md) - [AI Coding Toolkit — Harness Engineering](/canon/resonance/ai-coding-toolkit.md) — the sibling resonance; same layer argument, one tier down --- ## Open Pushback (folded in unchanged, 2026-09-21) Two fresh-context validators graded this page against rubric A–G. Fable: *land with listed edits*. Astra: *return to author*. The captain ruled: ship as-is with the pushback recorded, then test against real evidence. Nothing above was rewritten to absorb these; they stand as objections the bake-off must answer. Full verdicts: kitchen `rail/.../2026-09-21-jev-system-one-resonance/VERDICT.md`. **Corrections both validators agree on (not yet applied):** - "10x the latency" is 5x (anisselbd). "~10x cheaper" is 2.7x — DMB's own headline disagrees with its own prices. - 95.0% is a fitted regression over five Jev signals, not decomposition alone. - The seven-stage "layer 4" collides with canon's four-layer model, where layer 4 is generation. Needs distinct names. - `jev-latest` is TypeSafe's alias, not Cloudflare's; responses carry the versioned id, so "silent" is overstated. The silent risk is Workers AI exposing bare `typesafe/jev` with no visible pin. - 67.8% comes from DataCamp's write-up, not the launch post text; attribute it. - Kirigami candidate: HYGIENE 13 declares that vocabulary open; a Choice closes it. Strike or rewrite as open-set. **Objections that go to the test bench (Astra):** - "Never gate" contradicts "Noul near 0.99 or do not gate." Define gate; remove any implied license to automate ODD's semantic gate. - Pruning can delete required governance without triggering fallback: §4 discards below threshold, §9 escalates below threshold, and the two quantities (relevance vs confidence) are never distinguished. A confident false-negative removes the rule the judge needed. The static fallback covers outage, not a successful wrong prune. **Test: seed known-required docs into the candidate set and measure how often the router drops them.** - The router state as shown (tool, tokens, cache, disclosure) cannot decide `body_worth_it` or next epistemic action; it can warn about payload cost. **Test: which fields actually move the decision.** - The 99% has no denominator. **Test must define the unit** (tasks, decisions, tokens, time), a quality-preservation condition, a held-out set, and a decision rule for acceptable recall loss. - "Width is free" is unsupported: DMB's flat latency is across option counts, not question counts; priorbench reports 800 judgments at 985 ms; TypeSafe caps 64K total and 32K state-plus-question. **Test: latency vs question count on real boarding catalogs.** - Search-cannot-rule-applicability is asserted, not shown; the bake-off must include a reranking baseline, not only lexical search. - TypeSafe's own jaggedness page (Jev 1.13): distractor-rich state reduces accuracy, adversarial state can steer answers, separately asked questions need not preserve logical identities. All three hit a context-pruning router. **Test with distractors present.** - The strongest opposing view is not fully answered. Better argument: audit-gates requires a clean session with structured findings; Jev cannot be that session. Not "no prose, no grounds." - Calibration maps and thresholds have no named owner or lifecycle; that is where thinness fails if it fails. - `oddkit_resolve` (1,200 calls/30 d) is missing from the telemetry table and the `next_tool` Choice. - Access is documented, not proven: no call has been made, so the gold set is not proven to be the sole blocker. **Standing:** Bide `waiting`. Retraction conditions above apply. Reversal is a result.