So in a lot of cases when we've used LLMs as a classification hack, we've burned a ton of tokens in reasoning and output that we didn't really need to use to interpret the final result. (And I'll just say that we may not have needed all of the output tokens, but that incorporating assessment along with scoring seems to provide more accurate results.)
This goes beyond just asking an LLM to assign an arbitrary number to a particular concept, which in most cases distributes less-than-correct statistically, although that didn't stop us from considering LLM as a judge to be a viable strategy.
So this basically gives us a different class of model to use when classification or decision making is the only need. It doesn't replace any of the narrative if you still need that. Coupled with the higher speed and lower cost, that's why everyone's excited about it.
So inputs and outputs of LLMs are tokens. Inputs to Jev are state (arbitrary strings/tokens) and, depending on the type of query, either an assertion, options, or choices. (All of those are also arbitrary strings/tokens). Outputs from Jev are probabilities. If it's an assertion, the probability that it is true. For options and choices, it's probabilities for each one, basically.
Because Jev answers so quickly and inexpensively, it's a likely replacement for complex, best-effort functions like `isSpam()`, where up until now the only nondeterministic way of implementing that was an LLM, which is slow, costly, and may produce invalid/corrupt output.
1) it's very fast (they claim 40-200x faster than frontier models [1], would roughly line up with it doing diffusion)
2) each answer carries a calibrated probability (ie. frequency of outcome is close to predicted)
Another point being that it doesn't reason, hence designed for "System One" tasks.
I wonder if in continuous control with discrete actions (eg. their DOOM demo) it can make sense to blend answer by confidence instead of taking the argmax.
[1] https://typesafe.ai/blog/introducing-system-one-models-and-j...
So at the end of the day the groundbreaking work wasn't the model itself inherently but the way it was trained and then the way the harness interacts with it.
So this demo here is showing the harness side of things afaict but then TypeSafe's Jev takes it a step further via a specific training regimine.
Does Jev solve this?