Top
Best
New

Posted by albelfio 15 hours ago

Introducing System One Models and Jev(typesafe.ai)
1401 points | 399 commentspage 4
vatsachak 14 hours ago|
It could be used for coding if you gave it an AST.

If you work at TypeSafe please try this.

Side note: This is probably how LLMs would perform with better encoders and next-latent prediction, so eventually those will beat this architecture out. Still amazing though.

ramon156 14 hours ago||
I've implemented tree-sitter in pi before, and while it works, I have no real proof it saves me tokens, or is more accurate. I think a better implementation is a model that's trained for AST's, not just "use tool, see what happens".

I'd love to do research on this when I have the time.

vatsachak 14 hours ago||
Cool project!

That's what I was insinuating through "better encoder"; the model creating more efficient representations of ASTs using something like JEPA

CompleteSkeptic 13 hours ago|||
the hard part for coding is actually state engineering (e.g. getting your dependencies in context) - we haven't even tried it yet (because my philosophy is we should automate the easy tasks before the hard and we've been working on getting the model smart on the former)

we do think there's a lot of potential though and do want coding themed releases soon

hunterbrooks 13 hours ago||
I could see Jev being great at finding key symbols in codebase before a code generation/code review task. I sent you guys an email (to hello@) about using Jev in Code Review for www.ellipsis.dev.
Escapado 14 hours ago|||
I saw the CEO reply elsewhere in the comments to some other question. Maybe he can shed some light on it. My gut feeling is that this is non-trivial and they did not get this to work (yet?), otherwise I can’t come up with a good reason as to why they would not demo that as I assume half of the crowd here (myself included) would line up as customers.
vatsachak 14 hours ago||
Yeah it would be quite trivial to try and implement an auto regressive AST generator for STLC with Jev provided that you had bounded variable names and integers.

As you said, if it worked, they would have demoed it haha

8note 10 hours ago||
im not seeing it.

youd ask it to pick a location on the ast to add something from the grammar?

i dont see how this stays confined well enough? make a new output space every time? does that end up auto-regressive?

_davide_ 5 hours ago||
This is too much for me. ML playing doom was a thing since before LLMs, decisions tree were always insanely and no one ever used then anyway, i can't see anything new in this yet everyone is treating this as a revolution. This technology was always there and quite easily accessible all along.
vopi 8 hours ago||
This is actually pretty cool. I think the undertalked about part of this for TypeSafe is that they can always "extract"/distill the frontier of this type of task from the newest LLMs for cheap. Jev seems seems to be GPT-6-Astra/Fable 5.1 but I imagine a bunch of training data is from earlier models?

Then, you can serve it faster/cheaper than the frontier LLMs. It's basically distilling a small but extremely common use-case from LLMs and serving it. Then RLCD comes into play to update weights when a new model comes out, etc.

Any thoughts on what the next potential "cheap" win to be distilled from frontier LLMs is? I'm going to need to play around with this.

tensegrist 13 hours ago||
what is the…epistemic status, for lack of a better way to put it, of the probabilities? what do they mean? what (probabilistic) guarantees do we have about, say, the responses to

- is the capital of france paris?

- it is august. is it raining in paris?

(forgive the examples; they're probably not semantically the sort of thing jev is trained to work on. but i figure the point translates to various kinds of questions that come up in "inner loop of agentic pid controller" contexts)

a normal text-generating model if asked to produce a number will also do that just fine. i assume in jev's case it was actually rled to essentially learn to express priors over things using its implicit world model, which definitely ought to help, but can we say more?

niutech 2 hours ago||
How does Jev compare with encoder language models like BERT/RoBERTa/DistilBERT, which could also be used for text classification?
Otterly99 2 hours ago||
Always exciting to see people working on novel models, rather than the Nth version of the same slightly tweaked LLM.

I'm very curious how much ressources are needed to run such a model. This could be a complete game changer for local applications.

padolsey 4 hours ago||
I'd love to know if Jev is still fundamentally LLM-shaped in architecture. Like is it using a single forward pass with a learned readout over the predefined options (i.e. a discriminative head on a transformer, no decoding), or something else? I did similar things for zero-shot criterion-based classification using a 4B Qwen model but could not reach the level of intelligence they've got here. Tho speed/cheapness was similar.
virajk_31 4 hours ago||
Great to see something new..

However I don't understand how are they claiming zero hallucination, how does giving confidence score fix hallucination? or am I missing something here?

flowerboy-t 3 hours ago|
do you all see the use cases being similar to what you might use Fastino's Gliner models for? i see similar differentiation from general purpose LLMs in the sense that they can take natural-language input and return outputs adherent to a user-defined schema.

https://fastino.ai/blog/gliner2-5-span-free-information-extr...

im thinking about how well Jev could be used to replace a current LLM-as-Judge evaluation workflows, specifically on chat transcript data (think ~1,500 tokens) i wonder if the reasoning usually required pushes it a bit out of scope. didnt see anything published about constraints on the state size, so would be curious to hear about that.

mary776 3 hours ago|
definitely seems like a modified version of GLiNER2 or 2.5: - encoder-based (no text generation) - multiple tasks in a single forward pass - deterministic outputs - constraint-based classification
More comments...