NewJev use cases
Runnable typed-decision examples combine Jev judgments with thresholds and deterministic policy checks.
Added to Jevfast
NewHow it uses Jev
The customer-support use case sends the ticket subject and message, account tier, recent refund count, order data, and refund policy as state. It asks Jev for a department Choice along with other support judgments. Code uses the department and confidence to select a queue, while separate checks determine priority, refund handling, and whether a person must review the case.
What Jev decides
Illustrative customer-support department choiceExample answers · not a recorded Jev response · Source ↗
Question 1 · department
YOUR APP
INSTRUCTION
Choose which team should handle the support ticket.
STATE
State contains subject, message, account tier, prior refunds in the last 30 days, order details, and the refund policy. Values depend on the individual support ticket; this is a source-defined request shape, not an observed Jev answer.
JEV · CHOICE
- billing
- technical
- sales
- account
- other
App workflow
- Assemble ticket state
The use case combines ticket, account, order, refund-history, and policy fields into one state object.
- Ask parallel support questions
One System One call asks for department and intent Choices, urgency and refund Nouls, and frustration and churn Scores.
- Route and apply policy checks
Code maps the department to a queue, applies confidence and urgency thresholds, checks refund eligibility, and escalates uncertain or human-review cases.
Why it is interesting
The routing label is one part of a larger typed decision path. The code combines it with intent, urgency, frustration, refund-policy checks, and confidence thresholds, so a valid team choice does not by itself trigger every downstream action.