- Inference for a bunch of open weights architectures
- Diffusion image generation fir Z ai turbo
- Vision input into LLM for inference
- Vulkan/fast CPU, optimized kernels
- Playground for testing
- Last but not least, system one fast inference mode with same API semantics as Jev
Decision models work by using a backbone model like qwen 3.5 9b, along with a special linear head that provides the readout for the forward pass.
I like that they're being up front about this. Benchmarks are a metric that can be gamed. They give you an approximate estimate of where things land, but you really need to test for your use case.
I imagine if I fine tuned one of the open weight models for my use case it would be possible to beat it, though, but as a general drop in decision model, I’ve not really seen much that beats it especially for the cost
Videos will be next.
As it's minor change did not expect much, but having a higher context helps for sure. I will own the errors for passing bigger context.
Very refreshing.
> For the builders AND dreamers
> Enter the danger zone at your own risk.
> Size does matter, apparently
> We’re trying something new out here: we’re going to treat you guys like adults
> Lots of people love to ask what kind of sci-fi we’re releasing next
That said, their docs are great and don't seem to include all the Reddit cringe.
I've yet to see any company match the copy writing skills of Valve though.
I guess their cheeky "Warning: AI Benchmarks, don't trust them" is their way out of that one.
What I had before was basically:
- 1 classifier question
- if ok, do some heavy computation
- after heavy computation, another classifier
So now what I do is:
- Jev with the 1st and 3rd classifier
- if ok, heavy computation
I can classify many things at once, and it's cheaper and faster than 1 for sure and 1 maybe classification that I had before.
My team hasn't finished writing their blog posts yet, but the customer demos [2] went out the moment TypeSafe took our call and sorted all the paperwork out.
There's a tiny section at the bottom of the demo which explains how it actually works (or the github repo is the code).
We have a single decision API[1] over all similar models, so we run evals across all the "System One" api products & definitely don't trust any benchmark that you haven't run. All standardized benchmarks have been benchmaxxed already.
PS: just in case it wasn't clear, the demo is a game where we play to calibrate the human vs machine decision making (or just do it in auto-pilot mode).
i used luna 5.6 as the ranker/filter to remove useless items from upstream rag(mixing embedding, regex etc) and it did a good job but took 5-10 seconds each time. now less than 1 second and no observable precision loss. hope it helps
If I remember well, in the background, it does the multi-choice question: "What is the component requested ? --> Calendar, Slider, ..."
Still waiting on Decisions API using Luna, as this what I was using before.
Run your own evals, folks.