Post
CommunityJev Guides & Articles
Introducing System One Models and Jev
The Hacker News launch thread for Jev, with the CEO agreeing the shape is a zero-shot classifier and commenters mapping it to encoders, constrained decoding, and typed classification.
- Format
- Post
- Reading time
- 3 min
- Published by
- Community
- Last verified
- Sep 2026
Works forJev for Classification
Used inJev for Gaming
Highlights
- The thread drew 1,955 points and 511 comments, with discussion of the Doom demo, typed answers, and what "cannot hallucinate" actually covers.
- CEO Diogo Almeida agreed the shape is a zero-shot classifier, saying he prefers "zero-shot" over "instruction-tuned".
- He said the architecture is close to the chest for now, with a paper under discussion, and pointed to data rather than architecture as the interesting part.
- Commenters mapped Jev to encoder-only transformers with scalar and ordinal output heads, GLiNER-style label-conditioned encoders, and constrained decoding.
- Skeptics argued type safety is not factual correctness and that a forced boolean answer cannot abstain on out-of-range input.
Watch out
Discussion is dominated by people reacting to the launch rather than API users, and the CEO's architecture answers stay high level.
Questions about this entry
Short answers drawn from the linked project or page.
The CEO in the thread describes text or structured state in and typed decisions out, with choice mapping to a match statement, score to sorting and noul to an if, and agreed zero-shot is the more accurate label rather than instruction-tuned. What sits inside is not on the record: he said the architecture is close to the chest with a paper under discussion, and pointed to data as the interesting part.
It is short for Bernoulli, confirmed in the thread after a reader guessed exactly that from the docs link. One commenter noted Bernoulli is the underlying distribution and asked why the name needs explaining at all. That is the full extent of the thread record; no published naming rationale goes beyond the Bernoulli shorthand.
No, and several commenters pushed on this. Type safety guarantees the response matches a schema you defined, not that the judgment is factually right, so a wrong answer inside a valid enum is still wrong. The related objection is that a forced boolean has no abstention path: on out-of-range input it must still return one of the two options you supplied.
Not in the captured portion. Nobody posts API results, latency numbers or traffic; the discussion is demos, architecture speculation and naming. The one operational comment came from a spam and phishing team saying they have reasons to call a model like this daily and would sign up, which is intent rather than evidence.
He conceded the comparison to LLM tokens is hard to understand, partly because output tokens are not comparable, and confirmed the shape as text or structured state in and decisions out. He also endorsed the description of Jev as a large classification model rather than a large language model, preferring the label zero-shot over instruction-tuned because the latter implies a particular distribution.
The most common misreading was that the demos show Jev producing output in parallel and cheaply versus an LLM writing tokens one at a time. One reader attributed the first side-by-side demo to that, and the correction in the thread is that the demo exists to demonstrate its speed. Another reader was confused by the first demo and was pointed back at the primitive docs before getting it.
Both are recorded and they differ. The launch thread in this capture shows 1,989 points and 520 comments, while the independent report quotes the same thread at 1,831 points and 480 comments. Comment counts on a live thread keep moving, so treat both as snapshots rather than as contradictory measurements.
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.