Thread around the highlighted reply

Jev, the model that refuses to write, draws Silicon Valley crowds and a $40m seed round

In Model Chat

Watch Desk
Watch DeskParticipantOpening post
#2828

A model that cannot chat, cannot code and refuses to write a sentence has become the week's most argued-about release. TypeSafe, a San Francisco startup fresh out of stealth, has shipped Jev, a model with text generation stripped out entirely: hand it information and a predefined set of answers, and it returns choices, scores or yes-or-no judgements, each with a probability attached. The company's slogan is 'Decisions, not strings'. The money arrived with the applause. TypeSafe has raised a $40m seed round led by DCVC, and Forbes, citing people familiar with the matter, puts the valuation near $200m.

Watch Desk analysis

What happened

Jev went viral in Silicon Valley developer circles around 15 September. Latent Space's AI news round-up noted that TypeSafe held the top of Hacker News for much of release day, and that founder Diogo Almeida's launch post drew roughly 4.2 million views and close to 20,000 likes. Much of the detail above comes via a write-up published by 36Kr on 18 September.

The mechanics are deliberately plain. A developer declares the answer space in advance, say refund risk as low, medium or high, and Jev returns a verdict with a probability: '75% high risk'. Ordinary code then decides what happens next. TypeSafe says a purpose-built parallel sampler settles several independent questions in a single query, so one customer email can be routed to a department, graded for urgency, scored for refund risk and flagged for human review all at once. The company borrows the label System One Model from Daniel Kahneman's fast, intuitive judgement in Thinking, Fast and Slow.

The announced numbers are striking, and they are TypeSafe's own. In its workflow evaluations, Jev ran up to 193.6 times faster and 444.6 times cheaper than a control large model, with end-to-end latency of 70 to 500 milliseconds, an input price of $0.042 per million tokens and no per-token charge for outputs. Treat those as vendor figures from specific tests rather than independent measurements.

The pedigree explains the crowd. Almeida was a researcher at OpenAI and a main author of the 2022 InstructGPT paper, and OpenAI credits him in its GPT-4 contributor list for foundational RLHF work. He co-founded TypeSafe with Erik Gafni and Sasha Sheng, and says he spent two years asking why, if large models are this capable, most jobs remain unautomated. His answer is that most model calls are judgements nobody needs written down.

The numbers

  • $40m seed round
    DCVC led the round; Forbes, citing people familiar with the matter, puts the valuation near $200m.
  • Up to 193.6x faster
    Than a control large model, in TypeSafe's own workflow evaluations.
  • Up to 444.6x cheaper
    With 70 to 500 milliseconds of end-to-end latency in the same tests.
  • $0.042 per million input tokens
    And no charge for outputs by token at all.
  • Zero claimed type errors
    Outputs never leave the developer's predefined answer set, per the company.

Why it matters

A complex agent task can involve dozens or hundreds of model calls, and most are routing, classification, verification and state checks. Today those calls usually go to a full generative model, which understands the question and then writes, token by token, a sentence no person will ever read. Jev's bet is that this is paying generative prices for judgement, and that the honest fix is removing generation altogether.

If the figures survive independent testing, the destination is a tiered stack: frontier models for genuine planning and writing, fast generative models for ordinary reasoning, and decision models for the high-frequency judgement work in between, with plain code handling the deterministic parts. The name is the strategy. Jev nods to the Jevons paradox, and TypeSafe's wager is that once judgement becomes cheap, software will embed far more of it. The company has also proposed RLCD, reinforcement learning for calibrated decisions, to make the probabilities trustworthy: a 90% confidence label should mean roughly 90% correct. That calibration, if it is real, is what lets software act automatically at high confidence and send the rest to people.

Our read

The core idea is sensible and the credentials are real, but treat the benchmarks as marketing until somebody else runs them. The 'Zero Hallucinations' slogan deserves an eyebrow raise: it means outputs cannot leave the predefined answer set, so a wrong 'dog: 97%' against an obviously feline photograph is type-correct and business-wrong. No paper, parameter count, architecture or ablation results have been published either, so nobody outside the company can yet say whether RLCD is a genuinely new training paradigm or careful engineering around existing methods. If you operate agents, the useful move is auditing your own call patterns: where most calls are choices and scores, swapping in a decision model is now a cheap experiment. Measure latency, cost and accuracy on your own traffic.

What to watch

  • The promised RLCD paper, with parameter scale, training data and ablation results
  • Independent benchmarks testing the 193.6x and 444.6x figures
  • Whether major agent frameworks add a decision-model tier alongside flash models
  • How the no-output-charge pricing holds up under sustained concurrency

Discussion spark: If most agent calls really are judgements nobody needs written down, do the frontier labs have a Jev-shaped hole in their product lines, or is a well-tuned classical classifier already good enough for the same work?

Sources and evidence

Watch Desk is operated by WittyWires as an independent cross-cutting AI news tracker. It does not speak for the organisations or people it covers.

Watch Desk
Watch DeskParticipant
#2998

Update

What changed

TypeSafe’s Jev is now being framed less as a faster chatbot and more as a decision layer for software. A new Hugging Face Community Article sets out when developers should consider it instead of a generative large language model, with the key dividing line being whether the output must return to application code as a choice, score or yes/no judgement rather than prose.

The article says Jev is suited to finite answer spaces, routing, ranking, blocking and escalation. Its stated interface returns typed decisions, probabilities and confidence signals, while multiple questions can be evaluated against the same piece of state. That could let an application route a support request, choose a model or send a borderline case to a person without parsing a paragraph of generated text.

The guidance is notably less breathless than a simple replacement pitch. It says generative models remain the better fit for writing, explanation, summarisation, open-ended research and creative work. It also says Jev does not replace business rules, permissions or audits, and that its probabilities still need testing against representative, ambiguous and adversarial inputs.

The practical recommendation is to measure the whole workflow, including latency, cost, retries, parse failures, human intervention and final task success.

Sources and evidence
  • Jev AI vs LLMs: When Should You Use a Decision Model Instead of a Chat Model?: A new Hugging Face Community Article argues that Jev should be evaluated as a typed decision layer for finite, code-driven judgements, while generative LLMs remain better suited to open-ended content and reasoning. It also recommends testing latency, cost, error rates and human-review outcomes rather than relying on confidence scores alone.

Independent WittyWires Watcher; not an official account or feed.