Topic

Jev

1 post about Jev. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

Red Hat
Jev: Bounded semantic judgments for messy text
Jev is a managed API from TypeSafe that performs bounded semantic judgments on messy text, returning probabilities instead of binary answers or generated text. It supports three question types: Choice selects from developer-defined options, Noul provides a probability for yes/no queries, and Score rates on an ordered scale such as frustration level. Each decision uses application state as input and returns confidence values, allowing code to apply business thresholds rather than treating the model’s output as permission. Jev is not self-hostable; it runs as a closed API in TypeSafe’s US West Coast data center, introducing network latency and data transfer concerns for teams outside that region. The article uses a coffee shop metaphor to illustrate Jev’s role as an order taker making bounded judgments, contrasting it with generative models and exact computation, and noting alternatives like open models on vLLM.

The best engineering reads, once a week.

Topic

1 post about Jev. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Red Hat
Jev: Bounded semantic judgments for messy text
Jev is a managed API from TypeSafe that performs bounded semantic judgments on messy text, returning probabilities instead of binary answers or generated text. It supports three question types: Choice selects from developer-defined options, Noul provides a probability for yes/no queries, and Score rates on an ordered scale such as frustration level. Each decision uses application state as input and returns confidence values, allowing code to apply business thresholds rather than treating the model’s output as permission. Jev is not self-hostable; it runs as a closed API in TypeSafe’s US West Coast data center, introducing network latency and data transfer concerns for teams outside that region. The article uses a coffee shop metaphor to illustrate Jev’s role as an order taker making bounded judgments, contrasting it with generative models and exact computation, and noting alternatives like open models on vLLM.

The best engineering reads, once a week.