Stop generating text when all you need is a decision!
Jev is TypeSafe AI’s first “System One” model, built for a part of AI systems that we currently keep forcing generative LLMs to handle: making bounded decisions inside software.
Think about what happens during an agent run. The main model may be writing code, researching, planning, or reasoning through a problem, but the system around it is constantly making smaller decisions. Which model should handle the next step? Does this tool call need approval? Is the agent still making progress? Is the task actually complete?
Today, we often send those questions back to another generative LLM.
Even with structured outputs, the model is still generating tokens sequentially and constraining them into the schema we asked for. The application then takes that generated output and turns it back into the decision it needed in the first place.
Jev removes string generation from that loop.
You give it the current state and define the decisions you care about. Those can be a yes/no judgment, a choice between predefined options, or a score across an ordered scale. Jev returns typed answers with probabilities that the application can use directly.
That distinction becomes useful when these decisions sit everywhere inside an agent harness.
A coding agent can use the main LLM to understand a repository and write a fix, while Jev handles model routing, tool gating, risk checks, progress evaluation, or deciding whether another iteration is actually necessary.
And Jev should not become the permission system either. A probability that an action is safe is still a model judgment. Permissions, spend limits, allowlists, and other hard constraints should remain deterministic.
The architecture I find more interesting is the separation itself: generative models do the open-ended work, decision models handle fuzzy but bounded judgments around that work, and the runtime decides what is actually allowed to happen.
As agents become longer-running, the number of these small decisions only increases.
Using a full generative model for every one of them may turn out to be a very expensive abstraction.
If you want a deeper look at Jev, I also wrote a separate breakdown of how it works. I’ve quoted the article below.
显示更多