Triage policy checks 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 policy checks slice of the support triage pack. Intent: apply the Jev (TypeSafe System One) decision model to support triage policy checks. Primary search language: Triage Jev policy checks. 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
A policy check is a typed question whose instructions + criteria are your rules about the support ticket. Jev scores compliance; the intake router enforces. This is not a certification, and it is not a photocopy of a rival “policy engine” page — we keep rules atomic and ANDed in code.
Hub: Support triage hub. Compare, when the other tool is the real job: keyword triage.
Policy Checks inputs
Put policy text and the artifact in structured state (never hope the model memorized last quarter’s PDF):
{
"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" }
}Name ticket.body, policy.p1, customer.plan.
Decision signals and actions
| Id | Rule | Enforce |
|---|---|---|
pii_in_reply |
Drafted agent reply must not echo secrets from state | Jev Noul + template |
refund_cap |
Auto-refund flag only if amount extracted in code is under cap | code arithmetic |
safety_p1 |
Safety language in ticket.body → P1 hold | Jev Noul, then page |
Typical primitives on the same request:
| Id | Type | Job |
|---|---|---|
department |
Choice | billing / technical / sales / other |
frustration |
Score | calm → civil → strong language |
is_urgent |
Noul | time-sensitivity as P(yes) |
violations = [name for name, ans in policy_nouls.items() if ans.noul >= T_VIOLATION]
if violations:
return review(violations)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
Policy-in-state can be attacked (“ignore the policy”). High-risk paging on-call or issuing a refund flag still needs deterministic checks. 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
Gold labels are policy-versioned. A criteria edit without replay is how silent false-allows ship. 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 | you are here |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
One Score for “compliant”? No. Atomic Nouls per rule, AND/OR in code. Money and dates: extract in code first (jaggedness).
If a regex can enforce it, should I still call Jev? Skip Jev. Official “how to build” guidance: keep deterministic rules in code when you can.
Where is the rest of the Triage pack? Start with Triage decision workflow and Triage human handoff. 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.