Use cases· Last updated 2026-09-21

Logistics confidence thresholds 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 confidence thresholds slice of the logistics dispatch decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to logistics dispatch decisions confidence thresholds. Primary search language: Logistics Jev confidence thresholds. 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

Thresholds turn logistics dispatch decisions answers into act / review / abstain. They are product policy, not a hyperparameter TypeSafe ships. Official 0.5 / 0.9 sketches are illustrations. This slice also carries the false-reject discussion: over-gating logistics dispatch decisions hides calibration.

Hub: Use cases. Compare, when the other tool is the real job: logistics dispatch.

Confidence Thresholds inputs

You need (1) pinned answers on a frozen contract and (2) labels for exception gold from dispatchers, sla-risk gold, and whether escalate was justified. State 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

FLOORS = {
    "tag_exception_only": 0.55,      # illustrations — replace
    "auto_cancel_stop": 0.92,
}
NOUL_TAU = 0.78  # for sla_risk

def allow(ans, action):
    return ans.confidence >= FLOORS[action]

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

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.

Band around 0.5 on sla_risk always reviews. Do not copy 0.78 onto Choice confidence.

Evaluation and rollout notes

• Missed escalate on planted closed-dock + perishable notes
• False escalates (dispatcher fatigue)
• Wrong exception class at your floor

Fit loop: pin jev-1.13.0 → replay → plot error vs confidence → pick floors where auto-act error ≤ your SLA. 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

FAQ

Should auto_cancel_stop use 0.9 everywhere? No. Over-gating hides calibration and dumps the queue on humans. Fit per action.

Can I reuse a Noul τ as Choice confidence? No. Jaggedness: they are not interchangeable. See confidence.

Where is the rest of the Logistics pack? Start with Logistics decision workflow and Logistics human handoff. 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.