Logistics human handoff with Jev
Drivers and partners send messy exception notes. The TMS still owns routes, ETAs, and capacity. Jev classifies the exception text so code can pick a playbook. It does not solve VRP or promise a new arrival time.
This unofficial page is the human handoff slice of the logistics dispatch decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to logistics dispatch decisions human handoff. Primary search language: Logistics 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): Exception-class + SLA-risk on notes, with ETAs computed in the TMS — not a clone of a dispatch-optimization product page.
Logistics use-case context
Handoff is a first-class outcome for logistics dispatch decisions, not a failure of Jev. When the dispatch worker cannot auto-act, a human sees a packed exception note + SLA bands — not a chat transcript. We do not ask Jev to write the reviewer essay.
Hub: Use cases. Compare, when the other tool is the real job: logistics dispatch.
Human Handoff inputs
Humans should see what the model saw (filtered), not the warehouse dump you correctly refused to POST:
{
"note": { "id": "stop-441", "text": "Dock closed; guard says come back after 16:00." },
"sla": { "late_band": "30-60m", "priority": "p2" },
"playbook": { "redeliver": "Closed dock + next window same day → redeliver; perishable → escalate." }
}Decision signals and actions
| Signal | Typical reason enum (you name it) |
|---|---|
| exception other / low confidence | dispatcher_review |
| sla_risk mid-band | ambiguous_sla |
| disruption high | escalate |
| late_minutes ≥ HARD_SLA | escalate_sla |
These are application outcomes next to HTTP 200, not invented TypeSafe status codes.
Send the reviewer:
- stop id + filtered note
- TMS late minutes + playbook version
- answers + probabilities
- Play already applied (or not)
Do not treat a Noul of 0.5 as a “medium” logistics dispatch decisions 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 logistics dispatch decisions, treat auto_cancel_stop as the high bar (cancelling a stop or sending a customer a new promise time). 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 Logistics pack? Start with Logistics confidence thresholds and Logistics audit trail. Cluster hub: Use cases.
Will Jev reroute the truck? No. The TMS reroutes after your worker picks a play. Jev classifies the note.
Can we send a photo of the closed dock? Not to System One. Transcribe. Images are not accepted.
What this page does not claim
- Not a TMS, VRP solver, or SLA calculator.
- No on-time benchmarks.
- 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.