Jev support-ticket lab: three typed questions in one call
A free Jev lab shows how one call can return urgency, owning team and action deadline for a support ticket, with code routing by probability threshold to an LLM or a human, and lets you break the thresholds and fix them.
Jev + LLMs is f*cking insane... this free Jev lab is a clean blueprint for agent builders one support ticket enters. Jev reads the state and answers three typed questions in one call: noul → is it urgent? choice → which team owns it? score → how soon does it need action? then code reads the probabilities. clear, low-risk work flows to the right LLM. ambiguous tickets go to a person. refunds wait for approval. the draft gets checked against policy before it goes out the loop: ticket → typed questions → probabilities → threshold → LLM draft → approval / reply check → shadow run the best part of the lab: you can break the system yourself. set the threshold to zero, remove the “other” choice, watch routing fail, then repair it. the final exercise runs Jev beside existing rules on 40 tickets without letting it act the practical rule: Jev for bounded judgments, an LLM for writing, plain code for hard constraints save this, then read the article below to combine Jev with Dots ⭣
This post quotes another post: x.com/beamnxw/status/2105370052786565450