CommunityJev Media & Talks
A 200 millisecond decision, without streaming tokens
Dots and Arrows on production checks that need one answer in about 200 milliseconds, and why that is a different job from streaming tokens.
- Format
- Video
- Published by
- Community
- Author
- Dots and Arrows
- Last verified
- Oct 2026
Works forJev for Decision gating
Used inJev for Software & DevTools
Highlights
- The description's example is a single answer in about 200 milliseconds, not a generated paragraph.
- It contrasts that with a chatbot writing open-ended text.
- TypeSafe's own latency range on the docs is 70 to 500 milliseconds.
Watch out
The 200 millisecond line is the creator's framing of the job, not a measurement from this clip.
Questions about this entry
Short answers drawn from the linked project or page.
Framing, and the entry copy says so. The caveats state the 200 millisecond line is the creator's description of the job rather than something measured in the clip, and the captured source page is only the title and YouTube boilerplate.
Not on that number. The highlights record TypeSafe's documented range as 70 to 500 milliseconds, so a single round figure in a video title is the optimistic end of a wide band. Size your latency budget from the docs range instead.
It is a framing contrast, not a benchmark. The description and highlights only contrast one bounded answer against a chatbot writing open-ended text. Neither publishes request shapes, payload sizes, or numbers under concurrency.
The description's example is a check that needs one bounded answer quickly, contrasted with a generated paragraph. The source does not document input size limits, concurrency behaviour, or what happens when a check actually needs reasoning.
Dots and Arrows published it as a video explainer dated 3 October 2026, tagged for decision gating in software.
A production check that needs one bounded answer in about 200 milliseconds, which the highlights contrast with a chatbot writing an open-ended paragraph.
TypeSafe's own docs. The entry records that range as the documented latency, distinct from the single 200 ms figure used in the video's framing.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
YouTube: Dots and Arrows on a 200 millisecond decision that does not stream tokens.
Hacker News: Simon Willison's overview of Noul, Choice, and Score, and where a decision model fits.
benwerd53 pointsJev introduces a new shape of LLMRead the thread on Hacker NewsHacker News: swyx posts the Latent Space interview with Diogo Almeida.
swyx4 pointsJev: System One Models for Prod, Not God – With Diogo Almeida, CEO, TypeSafe AIRead the thread on Hacker NewsX: Diogo Almeida in five minutes
More Jev resources like this
Aishwarya Srinivasan's 22-minute end-to-end on using System One models inside software, instead of sending every structured check to a text model.
Jev Media & TalksVideo#community#video#architecture
Community
Max Jesch, on IBM Developer, walks Jev as a System One model that returns probabilities for classification instead of generating text.
Jev Media & TalksVideo#community#video#explainer
Community
Martin Keen, on IBM Technology, explains Jev as a System One model whose output is a decision rather than generated text.
Jev Media & TalksVideo#community#video#explainer
Community
LangChain maps Kahneman's split onto models: System 1 as the fast automatic decision, System 2 as the slow deliberate one, with Jev in the first role.
Jev Media & TalksVideo#community#video#explainer
Community
Ben Horowitz and Martin Casado interview Diogo Almeida on why capable models have not automated ordinary software, and what Jev is for instead.
Jev Media & TalksVideo#community#video#explainer
Community
India Jade explains RLCD as a response to using a frontier model for a small decision, which is the job TypeSafe trains Jev for.
Jev Media & TalksVideo#community#video#explainer
Community
From the Jev community
Posts from builders shipping with Jev right now.