Triage evaluation with Jev
Incoming tickets need a queue, a temperature reading, and a sense of time pressure — then code routes. Jev judges; it does not write the reply.
This unofficial page is the evaluation slice of the support triage pack. Intent: apply the Jev (TypeSafe System One) decision model to support triage evaluation. Primary search language: Triage Jev evaluation. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): Full triage pack (contracts → thresholds → handoff → audit) beats a single support-triage-choice recipe. We do not clone rival recipe IA.
Triage use-case context
Evaluation for support triage is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: queue gold, urgency gold, and whether a human would have paged. We publish no unofficial accuracy.
Hub: Support triage hub. Compare, when the other tool is the real job: keyword triage.
Evaluation inputs
Replay the same contract you ship:
{
"ticket": { "id": "T-1042", "body": "Card charged twice after the outage.", "channel": "email" },
"customer": { "plan": "pro", "open_incidents": 1 },
"policy": { "p1": "P1 = safety issue or complete outage" }
}Freeze questions, criteria, and jev-1.13.0. Record the response model.
Decision signals and actions
Score these, not a blog-grade star rating:
- Auto-route error rate at your floor (not a jev.pro leaderboard)
- False pages / missed P1s — tune
URGENT_TAUand the technical conjunction separately - Handoff rate: if everything pages, the floor is theater
Pair auto-act errors with handoff rate. If the intake router never acts, you have not evaluated support triage — you have evaluated a human queue.
Do not treat a Noul of 0.5 as a “medium” support triage score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Promote a threshold only when the harness says auto-act error ≤ SLA and reviewers still catch the residual. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For support triage, treat page_oncall as the high bar (paging on-call or issuing a refund flag). Tune on labels — see offline evaluation.
Evaluation and rollout notes
After any criteria edit, rerun before production. Cookbook lifts you see on TypeSafe pages are vendor claims — re-measure on your support tickets. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | you are here |
| Shadow → canary | production rollout |
FAQ
Will jev.pro publish a leaderboard for this use case? No. Measure on your labels. Vendor cookbook figures stay labeled as vendor claims.
What must stay frozen? Questions, criteria, and the pinned model id. Aliases can move.
Where is the rest of the Triage pack? Start with Triage failure modes and Triage production rollout. Cluster hub: Use cases.
Can Jev replace the support agent? No. It classifies and scores. Agents, macros, or humans act. See the support triage hub.
Should every company copy TypeSafe’s 0.5 intent floor? No. Official numbers are illustrations. Fit on offline evaluation.
What this page does not claim
- No invented triage accuracy or SLA.
- Schema-safe
department≠ the customer named the right product. - Not official TypeSafe documentation.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.