This is a good product but the naming/branding is pretty unfortunate. Typesafe.AI sounds like some typescript/structured output type of tool… What even is “system one” ? IMO the product/tech is really there, just needs better communication.
Introducing System One Models and Jev
161–170 of 512 posts
Re: Introducing System One Models and Jev
#162> we assume there is a correct compute graph (a “workflow” represented in code) and use the predictions of the largest, smartest, and most expensive external models as reference probabilities. ... Rephrased: every model gets the same workflow. We test how they compare to the average of the smartest models (in this case, Astra and Fable).
They assume there is a correct graph, but they don't compare to that, they compare to the average of the smarts models? So the smartest models are getting it wrong but you compare that anyway as a benchmark? So the outcome is "how much of a Fable am I getting" etc. Why not compare the actually correct thing?
But then even on this hand constructed eval, the first plot is showing Jev at less than Sonnet 5 accuracy. It is barely better than Luna. There are two Opus 5's and two Sonnet 5's without explanation. What is the plot showing?
I gave up.
Re: Introducing System One Models and Jev
#163Is the tradeoff of the parallel output that we don't get arbitrary string generation? like output # of tokens is fixed ahead of time? Either way, really cool and impressive.
Re: Introducing System One Models and Jev
#164This puts the human even more out of the loop I'll guess?
Re: Introducing System One Models and Jev
#165This sort of stuff almost sends shivers down my spine, it's like i'm looking 5 years into the future.
Re: Introducing System One Models and Jev
#166Is there anything published on how it maintains calibration? Or when you say "outputs calibrated probabilities" you mean "as calibrated as frontier LLM models, just cheaper" - which is a different claim; as LLM's aren't particularly well calibrated
Re: Introducing System One Models and Jev
#167Can this be used in practice to write code?
Re: Introducing System One Models and Jev
#168Earlier quoted context omitted.
I don’t think it’s misleading if you compare on the use cases they suggested. It’s faster and cheaper (no idea if higher quality), so it’s immediately interesting for certain things. And if you buy their RLCD claims, this might be even better than huge models that know a bunch of irrelevant things.
What was misleading was the original title: "Jev: New frontier model 40-400x cheaper and 20-200x faster" I'm not the gatekeeper of who gets to call themselves a frontier model, but I don't think most people would count Jev in that group. It sounds false. If their specific claims hold up, then it would make more sense to say something like: "Advanced the speed/cost frontier for structured decisions"
I think AlphaFold and related are also frontier models.
Being an LLM does not seem like the qualifier for frontier.
Re: Introducing System One Models and Jev
#169Earlier quoted context omitted.
CEO here - that is right! I do agree that the comparison to LLM tokens is hard to understand (also because output tokens are not comparable). But yes, text or structured state (like a JSON with multiple pieces of text in) -> decisions out (e.g. choice maps to "match" statement, "score" maps to sorting, "noul" short for bernoulli maps to if-statements)
Hi - first congratulations, System One looks really promising. The Doom demo really help me, at least, to understand how System One differs from LLMs. However the first demo (Side-by-side demonstration) - I'm struggling to understand what is going on here!
Re: Introducing System One Models and Jev
#170They claim it's not an LLM, which I read as "not an auto-regressive token generator". I assume they are still using a transformer, otherwise they would be talking about the thing that's not a transformer, instead of all the fluff on the linked page. But they emphasize parallel generation, so is it like a text diffusion model?