Logistics failure modes 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 failure modes slice of the logistics dispatch decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to logistics dispatch decisions failure modes. Primary search language: Logistics Jev failure modes. 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
Logistics dispatch decisions breaks in product-specific ways. This page lists those modes so you can write tests — not a generic “AI can be wrong” essay, and not a rival limitations-page clone.
Hub: Use cases. Compare, when the other tool is the real job: logistics dispatch.
Failure Modes inputs
Many failures start as contract violations (GPS breadcrumbs, a day’s manifest, missing note text). Canonical shape:
{
"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
- ETAs and VRP live in the TMS (compare).
jev-1.13is weak at comparing 47 vs 50 late minutes — computelate_minutesin the TMS and compareHARD_SLAin code (official jaggedness).- A dock photo becomes a confident
closed_dockif you invent a transcript instead of failing closed. - A 200 OK is not a clean dispatch decision.
- Invented on-time or miles-saved numbers.
HTTP vs application:
| You see | Class | Logistics move |
|---|---|---|
| 401 / 422 / 429 / 529 | Documented HTTP | Fix key/body or back off — errors |
| 200 + flat confidence or Noul ≈ 0.5 | Low confidence | Dispatcher review; do not cancel a stop or send a new promise time |
| Empty gather | Missing evidence | Skip Jev or ask “is enough information present?” |
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
Fail closed: do not cancel a stop or send a customer a new promise time. Schema-safe answers are not factual correctness. 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
Your canary set should include each bullet above.
- False auto-cancel on a planted “maybe closed?” note
- False-escalate rate (dispatcher load)
- Disagreement after a playbook-text edit
- Alias drift when someone ships
jev-latest
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 | you are here |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
If the API returns 200, is the decision good? 200 only means the call parsed. Low confidence, Noul ≈ 0.5, or a playbook miss are application failures.
Where do official weaknesses live? TypeSafe’s jev-1.13 jaggedness note — distractors, arithmetic, adversarial content. We do not invent more.
Where is the rest of the Logistics pack? Start with Logistics evaluation and Logistics decision workflow. 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.