Logistics production rollout 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 production rollout slice of the logistics dispatch decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to logistics dispatch decisions production rollout. Primary search language: Logistics Jev production rollout. 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
Production rollout for logistics dispatch decisions is Operate-pillar work: pin, shadow, canary, abort. It is not a launch-checklist clone of a rival “build with System One” guide — we only talk about this pack’s blast radius (cancelling a stop or sending a customer a new promise time).
Hub: Use cases. Compare, when the other tool is the real job: logistics dispatch.
Production Rollout inputs
Ship the contracted payload, the pinned id, and a documented safe default when the API is unavailable:
{
"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
| Stage | What changes | Logistics rule |
|---|---|---|
| Shadow | Nothing customer-visible | TMS plays unchanged; log Jev exception beside the stop. |
| Canary | One low-blast slice auto-acts | Auto-tag closed_dock only; cancels and new promise times stay human. |
| Abort | Auto-act off | Playbook or SLA-band change → freeze auto_cancel_stop; replay on the pinned id. |
Keep the workflow code you already designed:
def dispatch_act(ans, late_minutes):
ex = ans["exception"]
if ex.confidence < FLOOR or ex.choice == "other":
return "dispatcher_review"
if late_minutes >= HARD_SLA: # TMS math
return "escalate_sla"
if ans["sla_risk"].noul >= T_ESC or ans["disruption"].score >= 2:
return "escalate"
return f"play:{ex.choice}"
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
Safe default if System One errors or confidence is low: do not cancel a stop or send a customer a new promise time. 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
Promotion gate = evaluation green on the pinned id + audit traces for the canary. 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 | evaluation |
| Shadow → canary | you are here |
FAQ
Can I ship on 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. Shadow first.
What is the safe default if System One is down? Fail closed on cancelling a stop or sending a customer a new promise time. Do not guess.
Where is the rest of the Logistics pack? Start with Logistics evaluation and Logistics confidence thresholds. 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.