Show Notes
Jev, a new AI model from TypeSafe AI, skips the conversation entirely and makes a decision instead — a fast, structured output your software can act on directly. This episode looks at Jev and TypeSafe's new "System One" model category, a name drawn from Daniel Kahneman's distinction between fast, intuitive System 1 thinking and slower, deliberate System 2 reasoning. Instead of generating a paragraph and asking an application to interpret it, Jev takes application state plus defined questions and returns typed decisions with probabilities and a confidence estimate, suited to the many small judgments inside modern software and AI agents.
A support-ticket example shows how this works in practice: a message saying a customer was charged twice gets evaluated for routing, escalation, or human review, and the application branches on the returned values instead of parsing a generated sentence. Jev supports three decision patterns: choosing from a defined set of options, scoring something on an ordered scale, and producing a yes-or-no probability, with multiple questions evaluated against the same state.
TypeSafe says Jev generates its outputs in parallel and reports response times of roughly seventy to five hundred milliseconds. The company lists input pricing at four cents and two-tenths of a cent per million tokens, or forty-two dollars per billion input tokens, with output listed as free — TypeSafe's own published figures, worth treating as vendor-reported performance and pricing rather than an independent benchmark.
There's a limitation developers need to keep in mind: structured output doesn't guarantee correct decisions. TypeSafe's own customer agreement states its services can produce inaccurate or erroneous output, so production systems still need evaluation, thresholds, monitoring, and human review where the stakes are high. The episode closes by placing Jev alongside traditional software rules and general-purpose language models, in the space of routing, classification, guardrails, and the other decisions agent workflows have to make constantly.
Sources & References TypeSafe AI: Introducing System One Models & Jev — https://typesafe.ai/blog/introducing-system-one-models-and-jev TypeSafe AI: Home / System One Models and Jev — https://typesafe.ai/ TypeSafe AI: Master Customer Agreement — https://typesafe.ai/legal/mca
Voice narration is AI-generated.
More from Learn AI in Bits
A wave of cybersecurity disclosures has made this week feel like a turning point, with people calling it "Black October." This episode treats it as a cluster of high-impact incidents, not proof that one AI-driven campaign caused them all, and separates where AI was directly involved from where the failures were conventional.
Recursive self-improvement is the idea that an AI can improve the very process it uses to improve itself, and this episode separates what's been demonstrated so far from the dramatic predictions often attached to the term. It draws a clear line between self-correction (revising one answer), automated optimization (keeping the best of several tested variants), and true recursive improvement, where the system changes the process that generates future improvements, so the next round starts with a better improver.
This week's AI News Sunday Wrap-Up covers a week where the industry moved on several fronts at once: new flagship and open models, enterprise agent governance, a serious safety warning, legal pressure, and the physical infrastructure limits behind the AI race.
Meta's Muse story is moving fast, and this episode takes a closer look at Muse Spark, the multimodal reasoning model family behind Meta's push into AI agents, including yesterday's release of an open-weight version for developers.
When a large language model generates text one token at a time, even a fast GPU hits a sequential bottleneck. This episode explains speculative decoding, an inference technique that prepares several tokens at once and checks them together, and when the extra computation pays off.