This New AI Model Refuses to Write Text. That Is Exactly Why It Runs 100x Faster

TypeSafe AI, a stealth-stage startup founded by former OpenAI researcher Diogo Almeida, released Jev on September 15, a non-autoregressive model that generates no text and instead returns full probability distributions over predefined questions in a single parallel pass. The launch drew 1,655 points and 456 comments on Hacker News, with developers scrutinizing the startup's claim that Jev "can't hallucinate" and its pitch that code should own control flow while the model handles narrow judgment calls. Almeida framed the model as "a frontier-intelligence function call: unstructured state in, typed probabilistic decisions out.

The most discussed launch on Hacker News this week was not another chat model. It was a model that cannot chat at all. TypeSafe AI, a startup founded by Diogo Almeida, who previously worked on the instruction-following research behind ChatGPT at OpenAI, released Jev on September 15, the first of what they call System One Models. The post hit 1,655 points and 456 comments within a day, which for a closed-source model from a stealth-stage startup is remarkable. Half the thread is excitement. The other half is developers doing exactly what developers should do with a claim this bold: taking it apart. After reading the full announcement, the official documentation, and most of those 456 comments, here is what Jev actually is, which claims survive scrutiny, and when this model class matters for the software you build. Every mainstream model you know, GPT, Claude, Gemini, Llama, is autoregressive. It writes its answer one token at a time, each token conditioned on the last. That is what makes it able to produce essays, code, and refusals. It is also why a frontier model takes 3 to 329 seconds end to end, and why output tokens cost around 5x more than input tokens. Jev gives all of that up. It generates no strings, ever. You send it a state text or a JSON object plus a set of pre-defined questions, and it returns a full probability distribution over the options you listed, computed in a single parallel pass. No decoder, no token stream. Per the announcement: The name is a Kahneman reference. System 1 is fast, automatic judgment. System 2 is slow, deliberate reasoning. Jev is explicitly betting on the first one. Almeida's own summary: "Think of Jev as a frontier-intelligence function call: unstructured state in, typed probabilistic decisions out." The API has exactly three question primitives, and that constraint is the whole design. The following examples are from docs.typesafe.ai. A support-triage request from their docs looks like this: python from typesafe sdk import Choice, Noul, Score, TypeSafeClient with TypeSafeClient as client: response = client.system one state={"ticket message": "I was charged twice. Please fix this ASAP."}, questions={ "billing": Noul instructions="Is this ticket about billing?" , "tone": Choice instructions="What is the customer's tone?", criteria={"calm": None, "frustrated": None, "angry": None}, , "urgency": Score instructions="How urgent is this ticket?", criteria= "can wait", "this week", "today" , , }, Every question sees the same state, is evaluated independently, in parallel, in one request. Your code then composes the answers: threshold the probabilities, branch on the choice, escalate to a human when confidence is low. The docs are refreshingly opinionated about this. Keep deterministic rules in code. Ask narrow questions, not "analyze this ticket." Treat the model as a fuzzy if-statement, not an agent. That last part is the real architectural statement. TypeSafe is not selling agents. Their docs describe the target as AI-powered software: code owns the control flow, the model handles common-sense judgment over unstructured data, and it appears only where you need it. One CEO reply in the HN thread confirmed the philosophy: constrained decoding, the JSON-mode feature every LLM provider ships, "make models dumber unfortunately," because masking logits on a model that wanted to emit something else means the model was already confused. The boldest line in the announcement is that Jev "can't hallucinate." The comment section did not let that slide, and the truth is more interesting than the marketing. The narrow claim is true by construction. Hallucination in the LLM sense means generating fluent, confident text that is wrong. Jev produces no text. It can only return a valid value from the schema you defined, so it can never invent a field, a URL, a citation, or an API call that does not exist. As one commenter put it, "It just can't make up data." Type safety is guaranteed mathematically, and the company points out that a single counterexample would falsify it. The broad claim is false, and to their credit the CEO said so in the thread himself. When a commenter noted that a model "can still emit a completely wrong valid value," Almeida agreed: "that is likely true of all ML perhaps we could debate semantics, but I don't think it's fair to say a random forest 'hallucinates' in the way LLMs do." Another commenter gave the concrete failure: ask whether the user wants a human support agent, get "yes," when the real answer is "yes, but not right now." A human would attach that caveat. A constrained classifier cannot. A Jev-style model can route a billing query to the wrong department with perfect type safety and total confidence. The honest translation is this: Jev cannot produce malformed output, and it attaches calibrated confidence to every answer so your code can decide when to act and when to escalate. It can absolutely be wrong. "Cannot hallucinate" and "cannot be wrong" are different claims, and only the first one holds. The single most useful comment in the thread came from a developer who cut through all the branding: this is "basically a zero-shot classifier that can accept raw text or structured text as an input, and is able to classify that text as accurately they claim as a frontier-level LLM." The CEO's reply: "exactly right " That framing explains both the hype and the skepticism in one move. The most concrete evidence is a Doom demo, of all things. Jev played the game at around 10 decisions per second off structured game state, at roughly $7 per hour of play. One commentator's skeptical note is worth keeping in mind: the model sees structured state as text, which is not how a human experiences the game, and a non-AI bot could play better. What the demo actually proves is narrower and more important: judgment at game speed, in a real-time loop, for pennies. That is the product. Jev is in early access, closed source, with a 32k context window and no public benchmark scores. I have not used it, and neither has almost anyone outside the waitlist. So here is the checklist I would use, based on what the company itself documents: The pragmatic play for most teams is not replacement. It is audit: find the LLM calls in your stack where you throw away 90 percent of the generated text and keep a yes/no or a category. That is the surface this model class attacks first, and per the buzz in the thread, someone will ship an open-weight version of the idea soon. The bet that cheaper judgment creates its own demand is the most interesting part of the whole launch, and it does not require Jev specifically to win for it to matter. I write about AI engineering and backend development every week. Subscribe, it is free. Have a workflow in your stack that this checklist flags? I am curious whether the classification-shaped share of your LLM bill is as big as the thread suggests. Tell me what your split looks like in the comments.