Routing human handoff with Jev
Not every request deserves the same handler. Jev classifies cheaply; code sends work to a lookup, a specialist LLM, a costlier model, or a human.
This unofficial page is the human handoff slice of the intent and model routing pack. Intent: apply the Jev (TypeSafe System One) decision model to intent and model routing human handoff. Primary search language: Routing Jev human handoff. 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): Routing glossary + compare vs rules/queues; ranked-route floors. Not a clone of a rival intent-routing glossary page.
Routing use-case context
Handoff is a first-class outcome for intent and model routing, not a failure of Jev. When the front-door router cannot auto-act, a human sees a packed latest user request — not a chat transcript. We do not ask Jev to write the reviewer essay.
Hub: Intent routing. Compare, when the other tool is the real job: rules and queues.
Human Handoff inputs
Humans should see what the model saw (filtered), not the warehouse dump you correctly refused to POST:
{
"user": { "message": "Where is order 8831?", "locale": "en" },
"session": { "authenticated": true, "plan": "free" },
"catalog": { "handlers": ["order_status", "product_question", "return_exchange", "complaint", "other"] }
}Decision signals and actions
| Signal | Typical reason enum (you name it) |
|---|---|
intent.confidence below floor |
uncertain_intent |
intent.choice == other |
unmapped_handler |
| Complaint + high complexity or low Score confidence | complex_complaint |
| Ranked runner-up close to argmax (your margin rule) | ambiguous_rank |
These are application outcomes next to HTTP 200, not invented TypeSafe status codes.
Send the reviewer:
- user.message as sent
- intent probabilities (not just argmax)
- complexity score if asked
- handler your code selected
- whether a costly model would have been invoked
Do not treat a Noul of 0.5 as a “medium” intent and model routing score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Do not page humans on a single Score unless your conjunction says so. Pair with confidence thresholds. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For intent and model routing, treat complaint_auto_llm as the high bar (opening a refund/complaint LLM path or jumping to a costly model). Tune on labels — see offline evaluation.
Evaluation and rollout notes
Write the gold label back into the offline set. That is how floors move. 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 | you are here |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is handoff a Jev failure? No. It is a first-class outcome. Abstention is “no auto action”; handoff is the queue you send that case to (glossary).
Should Jev draft the reviewer note? No. Send structured answers. Generation is the wrong job.
Where is the rest of the Routing pack? Start with Routing confidence thresholds and Routing audit trail. Cluster hub: Use cases.
Is intent a reserved API field?
No. You name the key. See glossary: intent.
When do rules beat Jev? When the route is already in structured data. Compare traditional routing.
What this page does not claim
- No claimed win-rate versus regex routers.
- LangChain
ModelRouterMiddlewareAPIs are LangChain’s — believe their docs if they move. - Not official TypeSafe.
- 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.