What is a System One model?
A System One model is TypeSafe’s name for a class of models built to make fast, structured decisions that software can use directly. The official concept page says a System One model evaluates a state and returns typed answers and probabilities.
Jev is the flagship and the first model in that class. Like an LLM, it understands natural-language input. Unlike an LLM, it does not emit free text. You define the possible answers through primitives: Choice, Score, and Noul.
Why the name
TypeSafe says the name comes from Daniel Kahneman’s Thinking, Fast and Slow. System 1 is fast and intuitive; System 2 is slower and more deliberate. The emphasis here is on fast, focused judgments — the kind of call a knowledgeable person could make in a few seconds given the right context.
The launch post notes that “System 1 thinking” has also implied error-prone. TypeSafe writes that it believes System One models can be made more reliable than the alternatives, and defers the longer argument.
How TypeSafe contrasts it with LLMs
From the System One page and the launch comparison:
- Training target. System One models are trained for calibrated decisions. Probabilities are optimized against outcomes to reflect uncertainty. Calibration is measured across groups of predictions; it does not guarantee that any single answer is correct.
- Outputs. Possible outputs and structure are defined in advance. The model returns values inside that structure.
- Sampling. TypeSafe describes parallel evaluation of questions rather than token-by-token generation.
- Role in a product. Code owns control flow. The model supplies snap judgments.
A refund-shaped workflow
The official page walks a refund request:
- Build a state with the customer message, transactions, and policy.
- Ask independent questions together: was a refund requested, does evidence show a duplicate charge, does policy support a refund.
- Combine answers with deterministic checks, then route for action or review.
That pattern — decompose, ask in parallel, compose in code — is the System One design loop. See atomic questions and how to build.
Sources
Public TypeSafe or adjacent documentation only. No private claims.