The big deal is speed (high) and cost (low). This week I’m messing around augmenting mouse and keyboard interactions in an application with Deepgram + System 1 (Jev).
You can talk to an application and have it respond in real time with this combo. It’s clear this kind of general purpose intelligence may be a new development primitive.
However, at this stage, it’s difficult to work with for a few reasons. It’s API only, and you have to shape calling software to the way it communicates.
It’s not clear yet if what we’re missing is a new programming language, or some kind of harness or tool over the capabilities. LLMs were like this early on as well until better harnesses came along and reduced friction in their use.
Down the road, I highly suspect we’ll see:
- Intelligent context assembly using System 1 that summons memories as needed in LLM conversations and handles simple commands.
- System 1 programs that run in the datacenter and reach out to the request initiator on specific instructions like a CPU that has hit a memory barrier.
To get calibrated probabilities sounds like a very good feature, if they are indeed well calibrated.
And in my experiments even Qwen 3.8 has a hard time to consistenly conform to a schema, requiring retries, JSON cleanup etc, so to have a model of similar quality (SemIf et al) that simply cannot deviate from the schema by construction could be very helpful.
But I still need to experiment with either Jev/SemIf myself.
> To get calibrated probabilities sounds like a very good feature, if they are indeed well calibrated.
This is a valid point.
> And in my experiments even Qwen 3.8 has a hard time to consistenly conform to a schema, requiring retries, JSON cleanup etc, so to have a model of similar quality (SemIf et al) that simply cannot deviate from the schema by construction could be very helpful.
Literally every inference framework supports constrained encoding. You can make the model choose only from allowed tokens and you can infer only the first diverging token.
It's baffling to me that no inference provider actually exposes this functionality, so you have to run the model yourself to do it.
"even Qwen 3.8 has a hard time to consistenly conform to a schema"
idk maybe this is a feature?
if some LLM model is wonky, it won't generate right json format, so I'll know for sure
but for Jev, it's 100% right format, so I can't know if it's gone wonky or not