WHAT NEW IN X10.30 FRI

AI collections from X · 22 collections · 61,986 posts

jevVIDEO

Anatomy of a Jev request: state, questions, and four question types

Explains how a Jev request is built: a state to judge plus parallel questions returning Choice, Noul, Score, or Box answers that drop straight into code.

Akshay 🚀
@akshay_pachaarArchived 10 days agoOriginally posted 2026.10.19
Akshay 🚀 @akshay_pachaarOriginally posted 2026.10.19
Open original on X

Anatomy of a Jev request! Wiring an LLM into code usually means asking for JSON, then handling every case where the output drifts from the schema. Jev, TypeSafe's decision model, doesn't write text at all. Every answer is one of the options you defined, with a probability attached, so the result goes straight into an if statement. A Jev request has two parts. The state is the thing being judged. It can be a customer message, a database record, or now a photo. The questions are the judgments you want back. You can send several in one request, and they all look at the same state and run in parallel. Each question has an instruction, which is the question written in plain words. Some questions also carry criteria, the set of answers Jev is allowed to return. There are four question types. 1) Choice picks one option from a list you define, like routing a ticket to billing, technical or sales. You get the option name plus a probability for every option. 2) Noul is a yes-or-no question. Instead of a hard yes or no, it returns the probability that the answer is yes, and your code decides the threshold. 3) Score places the state on an ordered scale you define, like how frustrated a customer sounds, from calm to very angry. The answer can land between two levels. 4) Box is new in the latest release. You ask where something is in an image, and it returns the four edges of a rectangle around it, as fractions of the image's width and height. Box always returns a rectangle, even when the thing isn't in the image. That's why it's usually paired with a Noul asking whether the object is there at all. Images come in through a new assets field. Each image gets a reference string, and wherever that string appears in the state, an instruction or the criteria, Jev sees the image instead. The full walkthrough, with the live demo and the code, is in my video quoted below on multimodal Jev. You can also watch it on YouTube: https://www.youtube.com/watch?v=ciQghn271rA

This post quotes another post: “Jev goes multimodal: image-based gesture and object detection decisions”

x.com/akshay_pachaar/status/2112119972914933988Archived 2026.10.20 10:07