USE CASE / Choice + Score
Document review triage
Choose fast path, request more data, or human review
Document, provenance, and applicable policy
Choice + Score
Choose fast path, request more data, or human review
Code validates required fields before queueing
Separate missing fields from hard judgments
A missing purchase-order number is a deterministic validation failure; ambiguous terms may need semantic judgment. Check format, access, amount, and duplicates before Choice routes to completion, data gathering, or review. A model result is not payment approval.
Three edge cases to test
- Missing PO number: request data
- Amount mismatch: rule block and review
- New layout with valid fields: test false alarms
Example request
This is a design draft, not an actual Jev answer or accuracy test.
{
"state": "Invoice missing purchase order number.",
"model": "jev-latest",
"questions": {
"decision": {
"type": "choice",
"instructions": "Which review path should this document enter?",
"criteria": {
"fast": "All required information is present",
"missing": "Required information is absent",
"review": "An ambiguous or high-impact issue needs a person"
}
}
}
}Limits and fallback
High-impact legal or financial decisions still need qualified owners.
What does the support team actually need to decide?
Follow one support ticket from raw text and verified facts through three questions, an illustrative answer, edge cases, and launch evaluation.
Worked example: design a Jev workflow for a missing delivery