Video
CommunityJev Media & Talks
I tried TypeSafe's System One model
Joe Maddalone on using Jev for routing and filtering before a generative model, with demo code in a transcript-analyzer repo.
- Format
- Video
- Reading time
- 2 min
- Published by
- Community
- Author
- Joe Maddalone
- Last verified
- Sep 2026
Highlights
- The description positions Jev as a typed probability engine for routing, filtering, and pre-processing before an LLM.
- It repeats the launch figures of 193x speed and 444x lower cost, with no output-token fee.
- Demo code is linked at joemaddalone/jev-transcript-analyzer-demo.
Watch out
The speed and cost multiples are the vendor launch claims as restated in the description, not a measurement from this video's repo.
Questions about this entry
Short answers drawn from the linked project or page.
They are vendor launch figures restated in the description. Nothing in the video or its repo produces them, so if the multiple matters to your decision you would need to reproduce it against your own traffic. They also assume no output-token fee, which is the main thing that drives them.
The framing is that Jev handles routing, filtering and pre-processing so the generative model is only called on the cases that need it. That reduces calls and tokens on a filtering job, but it also means a wrong filter silently drops work before the better model ever sees it.
Demo code is linked at a public repository, so you can. Nothing documents its dependencies, how it is configured, or whether it ships with the transcript data it analyzed, so expect to supply your own input before you get comparable numbers.
The video does not cover it. The failure mode of a cheap pre-filter is silent under-inclusion rather than a visible error, and the linked demo gives you nothing to build a fallback or a review queue from without measuring your own false-negative rate.
Joe Maddalone published it, with demo code linked at the joemaddalone/jev-transcript-analyzer-demo repository.
As a typed probability engine for routing, filtering, and pre-processing before a generative model, so the LLM is only called on cases that need it.
No. The entry says the 193x and 444x figures are vendor launch claims restated in the description, not a measurement produced by this video or its repository.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
YouTube: Joe Maddalone tries Jev as a routing and filtering step, with a transcript-analyzer demo.
X: Hard-coded rules moved to Jev
Facebook: Intake Router keeps diagnosis out of the answer space at the front desk.
FacebookClinicnotes
X: OpenRouter Decision Model Rankings
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.