Writing vs deciding: why Jev-style decision-only models are called a paradigm shift
demian_ai · x · 2026-09-23
A systematic breakdown of what Jev is and when to use it instead of an LLM.
- The split: LLMs answer "what should we say next" — even a yes/no requires writing tokens; Jev answers "what is this": text in (tickets, emails, app state), typed judgments out — yes/no probabilities, one-of-N picks, scale scores.
- Workflow: for a billing ticket, don't draft a reply — ask in parallel: is this billing? which team? how urgent? human needed? Results in a few hundred ms; your code owns the branching.
- Why fast and cheap: no autoregressive output tokens, one-pass scorecard fill, 70-500ms latency, input-only pricing.
- Paradigm: most production AI is secretly a decision model wearing a writer's clothes — prompting chat models for JSON, parsing, retrying on schema breaks. Jev removes that layer; the cost is it can't invent options or explain itself.
The shift, if real, is the writing/deciding split, not raw intelligence.
Related event: Jev Model Sparks Debate: A Dedicated Decision Layer Beyond LLMs(4 posts)→
More from coding & agent
- Loom founder launches Roma 2.0, a shared to-do list that orchestrates AI agents — thetripathi58 · 2026-11-12
- Sosumi Eval: Apple Docs Access Lifts Coding Agent Pass Rates from ~33% to 94-98% — JordanMorgan10 · 2026-11-12
- CypherGuard fixes structurally wrong LLM Cypher queries, hitting 88.5% on CypherBench — JeremyCMorgan · 2026-11-12
- Building an End-to-End Hedge Fund in Python with Claude Code: A 5-Step Workflow — mdancho84 · 2026-11-12
- Jeff Dean: comfortable with engineers spending up to $10M/year on AI tools — deedydas · 2026-11-12
- Developer builds VladOS, a personal life dashboard, by just describing it to an AI agent — haltakov · 2026-11-12