Logistics evaluation 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 evaluation slice of the logistics dispatch decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to logistics dispatch decisions evaluation. Primary search language: Logistics 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): 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
Evaluation for logistics dispatch decisions is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: exception gold from dispatchers, sla-risk gold, and whether escalate was justified. We publish no unofficial accuracy.
Hub: Use cases. Compare, when the other tool is the real job: logistics dispatch.
Evaluation inputs
Replay the same contract you ship:
{
"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." }
}Freeze questions, criteria, and jev-1.13.0. Record the response model. Pair each row with TMS late_minutes computed outside Jev — the harness must score the conjunction your worker actually ran.
Decision signals and actions
Score these, not a blog-grade star rating:
- False auto-cancel on a planted “maybe closed?” note
- False-escalate rate (dispatcher load)
- Disagreement after a playbook-text edit
- Exception ==
otherrate (coverage hole, not a model win)
Pair auto-act errors with handoff rate. If the dispatch worker never acts, you have not evaluated logistics dispatch decisions — you have evaluated a human queue.
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
Promote a threshold only when the harness says auto-act error ≤ SLA and dispatchers 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 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
After any playbook or criteria edit, rerun before production. Cookbook lifts you see on TypeSafe pages are vendor claims — re-measure on your exception notes. 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 Logistics pack? Start with Logistics failure modes and Logistics production rollout. 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.