
Prasenjit Sarkar on X: I keep seeing the same fix across agent stacks this week: teams are ripping the
@stretchcloud@stretchcloudlisted 47m agoreviewed by JevI keep seeing the same fix across agent stacks this week: teams are ripping the expensive model out of the middle of their decision loops. TypeSafe shipped Jev in early access on September 15. Not a chat model. They call it a System One model: hand it a state and typed options, it returns calibrated probabilities, no text generation at all. The mechanism is simple. Most agent loops burn a full LLM call on decisions that never needed generation: route to worker A or B, is this result relevant, approve or block this action. TypeSafe claims up to 200x faster inference and 400x lower cost on that class of decision. Ricker's own tests below land at 193x and 444x. What happened next is the real story. Within four days, Cognition's Jared Palmer shipped Kev, a LoRA adapter on Qwen2.5-0.5B trained in 1 hour 45 minutes on a MacBook Pro, with an API close enough to point TypeSafe's own SDK at it. Kev now scales up to a 9B version that trails Jev by about 4.5 points on held out evaluation. Laya-MLX arrived the same week targeting millisecond decisions on Apple Silicon. A community leaderboard, JevBench, already ranks a dozen of these models. The adoption signal convinces me this is not a toy. TanStack AI shipped a native decide() API for typed choices, scores and booleans. Beacon, an open source memory layer, uses Jev to score which coding sessions are worth turning into reusable lessons. Three teams, one primitive, inside a week. RouteLLM out of Berkeley showed back in 2024 that routing simple queries to a cheap model cuts cost over 85% while holding 95% of GPT4 quality, and production semantic routers report 40 to 90% savings today. What changed is that the router stopped being a side project and became a shipped, benchmarked model category with a name. The bottleneck this solves is real: every agent framework has a model sitting in a loop answering questions that never needed a sentence back. My read is that the decision layer becomes as standard a piece of the agent stack as the vector database became for retrieval, and whoever owns the default there owns a lot of the unit economics conversation for the next year of agent infrastructure. https://x.com/0xRicker/status/2101705843200721203 ❤️ 1 likes on X
- Author
- @stretchcloud
- Use case
- Benchmarks & Evals
- Added
- 2026-09-25
- Time
- 1 hour
All figures come from the author. Check the source before you quote them.
More in Benchmarks & Evals
- Morgan on X: It has been a really interesting experience to build an eval suite for System On▲ 0x.com
- silentguy on X: Grok Bot does the job, Jev decides where the job goes next▲ 0x.com
- spect on X: The founder of Jev just dropped a 1-hour masterclass on how Jev actually works▲ 0x.com
- Dain on X: A beautiful pattern can still be noise.▲ 0x.com
- Utkarsh Maheshwari on X: Is the Jev hype real,▲ 0x.com
- OpenMed on X: Four typed questions across four authored fictional notes, labels written before▲ 0x.com
Jev guides for this use case
- Using Jev as a judge for evalsGrading with a decision model instead of a prose-writing judge, and why calibrated confidence is the real prize.
- How Jev sorts a build into one of 21 use casesThe 21 criteria Jev classifies against, published in full, plus what the reviewer sees and how ambiguity is handled.
- Jev statistics: latency, cost, and this directory's own numbersPublished benchmarks with their caveat attached, plus live directory figures that update automatically.
Bid history
No bids yet — the first one takes this project straight to the spotlight.