From Text Generation to Decisions: Jev, Laya and the System One Shift
For ten years the road to artificial intelligence ran through the sentence. Models got better by saying things, were judged by saying things, and made money by saying things; every capability report ended with generated text doing something impressive. Then came a September week in which the newest, most-funded, most-discussed models in the industry arrived with their mouths closed. They classify, they score, they answer yes or no, and they produce no text at all. This is either a niche or a hinge, and the evidence so far reads like a hinge.
The week the category appeared
The commercial half arrived first. In mid-September 2026, TypeSafe AI ended two years of stealth with Jev, its first System One model, available in early access on a hosted API: unstructured state in, typed probabilistic decisions out, all outputs generated in parallel in a single query rather than token by token, trained with reinforcement learning for calibrated decisions on an architecture the company does not disclose.[1] The launch claims are aggressive, decision intelligence comparable to frontier models at two orders of magnitude faster and cheaper, and the launch post, to its credit, prints its own asterisks next to the biggest numbers.
Three days later, the open half arrived. A repository called laya appeared on GitHub, Apache-2.0, from Convai Innovations: a multilingual, non-autoregressive decision engine of a few hundred million parameters answering the same three question types, choice, score and yes/no, in one forward pass, on your own machine, in tens of milliseconds.[2] Within days the ecosystem had sprouted a third-party benchmark running both models on the same 500 labelled examples, a directory site, explainer posts, and an academic preprint naming the category “typed evaluation models” and dating its emergence to that same month. A category that gets named, benchmarked and catalogued inside four weeks is not a product launch. It is a turn.
I took the two models apart in an earlier essay; the point to carry here is what their pairing proves.[3] When the closed flagship and the open alternative land in the same week and the open one holds its own on the simple questions, the category has both an economy and a commons. That dual existence is historically the sign of the turns that last.
Why the outputs stopped
The sentence was always the interface, not the goal. When the only instrument was a text generator, every task had to be dressed as prose: ask a question, receive a paragraph, parse the paragraph, act on what you hoped it meant. Much of what software actually needs was never prose at all. Routing a ticket is a category. Triaging an alert is a severity. Blocking a message is a probability with a threshold. Paying a frontier model to generate a paragraph so that your code can read one adjective out of it was always an absurdity tolerated only because there was no alternative.
Now the alternative exists on both terms. The economics: the vendor claims two orders of magnitude on decision-shaped work, its own workflow evals reaching 193.6 times faster and 444.6 times cheaper, with the honest caveat that those are the high end of real-world gains and the pricing may be subsidized.[1] The open version’s price is the electricity to keep 322 million parameters resident, and its latency is 21 milliseconds, measured, on a laptop.[4] The reliability: typed outputs with calibrated probabilities cannot be hallucinated in the way prose can, because there is no prose, only a value from a schema and a number saying how sure. The privacy: a decision computed on your own hardware means the text being judged never leaves the room, which is the difference between a moderation bot that leaks its community to a vendor and one that phones no one.[5]
The wider condensation
Zoom out from the two flagships and the pattern is bigger than one category. Across the open-weights world, people are taking large language models and condensing them into small, sharp, non-generative things: decision models purpose-built as encoders, classifiers distilled from teachers, routers and guardrails tuned on synthetic data, narrow specialists bent out of general models by fine-tuning on a laptop GPU. Laya itself invites this: its repository ships a fine-tuning notebook that runs on free cloud GPUs, and a few hundred labelled decisions from your own domain take the model from 0.362 to 0.766 on its benchmark. The general-purpose model is becoming the raw material. The products are the condensates.
This is the frontier story at consumer scale, and it runs in the same direction. I have argued that the attempt to stop distillation must fail because capability leaks through every exposed interface; the same logic runs downward. Capability that condenses does not just flow from closed labs to open ones. It flows from big models to small ones, from datacenters to laptops, from APIs to weights, and at the end of that pipeline sits something no policy can reach: a few hundred megabytes that decide quickly, offline, forever.[6]
The case for the niche
The opposing case deserves its day, because hinges are declared monthly and arrive yearly. Most AI work is still prose work, and a model that cannot write is useless for it; the decision-model stack still needs an LLM behind it for everything it escalates, which means two systems to maintain. The measured weaknesses are real: graded and nuanced questions are where these models fall down, 35 percent on a five-star scale is a coin with extra steps, and calibration degrades exactly where judgment gets subtle.[4] The vendor’s Kahneman framing is a metaphor pressed into marketing service; System 1 in the book is not an architecture diagram. And a category that acquires directories and week-one listicles before it acquires a track record has resembled other summers that promised turns and delivered tools. Tools are not nothing. But not every tool is a hinge.
What survives that skepticism is the part I would bet on: open weights, small enough to run anywhere, doing a job software has wanted done since before the chat box existed. Policy cannot un-release them, economics cannot make free expensive, and the workloads they serve are counted in the billions per day: every filter, route, flag and gate in the world’s software.
The machines learned to speak, and everyone watched. They are now learning when not to, and almost no one is watching. That is usually how the important part arrives.
- TypeSafe AI, Introducing System One Models & Jev (September 2026): two years in stealth, early access, closed weights, API only; “a frontier-intelligence function call: unstructured state in, typed probabilistic decisions out”; parallel generation of all outputs in a single query; RLCD training; latency 70 to 500 ms; workflow evals of 193.6x faster and 444.6x cheaper described by the vendor as “on the higher end of real world gains”; “We can’t prove it isn’t subsidized.”
- NandhaKishorM/laya, Apache-2.0: “Multilingual, non-autoregressive System 1 decision engine. Typed decisions over 100+ languages in a single forward pass”; checkpoints
convaiinnovations/laya(English, 421M) andconvaiinnovations/laya-multilingual(322M); question typeschoice,score,noul; Kaggle fine-tuning notebook; typed-decisions checkpoint at 0.766 against 0.362 base. - From LLMs to System One Models: Jev and Laya, on what a System One model is, how Jev and Laya differ, and where each falls short.
- Laya: open-source alternative to TypeSafe Jev, the independent benchmark: 21 ms per decision on an Apple M1 Max; Laya at 96% on SMS spam and 35% on a five-level rating untuned; calibration error 0.05 to 0.06 easy, 0.34 to 0.40 hard.
- A Telegram Spam Bot on a Local Decision Model, a Telegram moderation bot running a local decision model; Calibrating Laya: Question Phrasing, Direction and Thresholds, on calibrating it.
- The Soft Target, on why distillation cannot be stopped and capability keeps condensing into smaller models; The AI Act Regulates Invoices. Open Weights Don’t Send Any., on the irreversibility of released weights.