TypeSafe's Jev returns typed decisions, not sentences — and a researcher says he built it first
TypeSafe's Jev returns typed decisions instead of prose, at 0.4s and $0.0004 a case. Two days later, a Reddit researcher claimed he got there first in 2025.
Vlad Makarovreviewed and published
On September 15, TypeSafe AI published Introducing System One Models & Jev and opened early access the same day. Jev is not a chatbot with a different system prompt. It generates no natural language at all: unstructured program state in, typed probabilistic decisions out, with the permitted answers fixed in advance by a schema. TypeSafe's framing is that this is "a frontier-intelligence function call." By September 17 the argument on r/LocalLLaMA was no longer about what the model does. It was about who did it first.
What the model actually returns
The launch post is signed by founder Diogo Almeida, who describes himself as having helped build the instruction-following methods whose work "ended up as the research behind ChatGPT," after "two years in stealth." The Register reports $40 million in funding and repeats the co-inventor-of-RLHF biography.
Three question primitives are documented: Choice (categorical), Score (numeric or rubric) and Noul (yes/no probabilities). Underneath sits a new architecture with a parallel sampler returning all outputs in a single query instead of one token at a time, trained by a method TypeSafe calls Reinforcement Learning for Calibrated Decisions, or RLCD, positioned against RLHF and RLVR. What the model does not return is prose. As the vendor concedes, it gives "a number, not a rationale."
Vendor numbers, vendor caveats
Every figure below is TypeSafe's own account, from a vendor-built evaluation of four workflows: security incident response, agent-trace observability, invoice processing and customer service.
| Model | Agreement with reference | Cost per case | Latency |
|---|---|---|---|
| Jev | 67.8% | $0.0004 | 0.4s |
| GPT-5.6 Terra | 67.9% | $0.0304 | 10.1s |
| GPT-5.6 Sol | 74.1% | $0.0836 | 23.3s |
| Claude Opus 5 | 73.1% | $0.1761 | 37.8s |
Other vendor-reported figures:
- Input pricing $0.042 per million tokens, or $42 per billion; output free, described as "too cheap to meter."
- End-to-end latency 70ms to 500ms, framed as 40x to 200x faster for System One-shaped queries.
- Structured output error rate 0%, which the company states is "not empirical," because schema matching is guaranteed: "This would be an easy thing to falsify with just a single counter-example, but it is mathematically impossible."
- Home-page headline figures of 193.6x faster and 444.6x cheaper.
TypeSafe also publishes the caveats a launch page would normally bury. The workflows are "not in our training distribution. However, they were made by individuals on our model capabilities team, so some bias could exist." The reference answer is "the average of GPT-6 Astra and Fable 5.1," which "biases answers towards OpenAI and Anthropic's models." The competitor structured-output numbers come from OpenRouter, "so, there almost certainly is bias here." On the business model: "We can't prove it isn't subsidized; we'll need the long-term to prove the sustainability of our pricing." And on the demo: "The relatively shorter input paints our model in an advantageous light."
The outside case against
Sean Goedecke's September 16 post, Jev means structured output is interesting again, argues that fast structured output already exists: prefill an ordinary LLM with the response prefix, generate one constrained token, and batch the questions. He reports "a 2x-3x speedup compared to non-prefixed structured output" with Qwen2.5-1.5B-Instruct and suspects Jev "does not have a substantial technical moat." On reliability he calls the hallucination-immunity claim "a semantic dodge": Jev "can absolutely still pick the wrong choice," it simply cannot phrase the wrong choice as fluent prose. Giving up test-time compute, he adds, probably caps the class around non-reasoning LLMs. The Register makes the same point, noting that Jev's output "is not natural language" and this "does not preclude the possibility of being incorrect." DataCamp's explainer goes further on provenance, labelling the whole benchmark set vendor-reported with "no large-scale independent reproduction" yet.
The prior-art claim
On September 17, u/Nandakishor_ml posted to r/LocalLLaMA (comments/1wijo3e, roughly 660 points and about 100 comments) claiming he built the same architecture "one year back," in March 2025, and open-sourced all of it: a paper, arXiv:2503.23303, a model and a dataset on Hugging Face under DeepMostInnovations, and a second paper from September 2025, arXiv:2510.01237. His method: PPO over sequence embeddings emitting turn-by-turn conversion trajectories with probabilities between 0.0 and 1.0, for sales conversations. Jev, on his reading, is parallel sampling trained with RLCD producing confidence distributions and schema choices — a vertical application against a horizontal one. "It's incredibly frustrating that the thing that you made with months of hard work, sweat and sleepless night is architecturally similar with the vertical use case and don't get the support you deserve because frontier lab build something horizontal." A near-duplicate thread appeared hours later, after Reddit's filters removed the first attempt.
Two accuracy notes. The architectural similarity is the poster's claim; nobody in either thread checks it, and TypeSafe has published nothing about RLCD detailed enough to evaluate as an algorithm. No one from the company responded.
How the thread split
Reaction divided along a familiar line. One commenter: "It's also always very easy to say 'that was my idea' when things are similar. Plenty of people created light bulbs of all kinds, but everyone knows Edison's name." Another put the asymmetry more sympathetically: "an idea can exist in public, with code, weights, data, timestamps, even a paper attached to it, and somehow still not fully 'exist' until an institution with enough gravitational mass says it again." A third was blunt about the missing evidence: "You can have the same idea but is the performance the same as jev? I don't think so." A fourth preferred a different playbook: "You need to say it's 'Too dangerous to release' then release it anyway." And one commenter noted that the prefixed-prefill replication Goedecke described was spun up in hours after reading the announcement — a quick counter-demo to a two-year stealth project.
What would settle both halves
The release and the dispute share one weakness: the only measurements are the vendor's, and the only description of the training method is a marketing name. An independent reproduction of the latency and cost claims on a neutral harness would test the numbers, and what actually improves when a model keeps working is the question our replay-simulator piece tackles from another angle. A published description of RLCD detailed enough to reimplement would test the method. Either a licence or permission statement from TypeSafe, or a citation of the 2025 papers as prior art, would settle the credit question. Until then, Jev is a genuinely unusual product with a genuinely unverified claim underneath it.
