Use cases· Last updated 2026-09-21

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

Evidence collection for logistics dispatch decisions happens before POST /v1/systemone. Jev does not browse your warehouse, retriever, or ESP. You gather the exception note + SLA bands facts, filter them, then ask snap questions. This slice is where fan-out cost math belongs: batch questions, do not re-send state.

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

Evidence Collection inputs

Collect:

• Exception note as text
• Playbook excerpt the Noul names
• Late band or minutes from the TMS — not “maybe an hour” for Jev to parse

Never send:

• Asking Jev for a new ETA or optimal stop order
• Live map screenshots
• The whole day’s manifest as distractors

Shape the payload like this once the gather step finishes:

{
  "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

Each evidence field should change a named answer:

Exception + disruption + sla_risk in one call per stop. Re-optimization is a TMS job after you choose a play.

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

If the gather step fails (empty exception note + SLA bands, redaction stripped everything, retriever empty), fail closed on cancelling a stop or sending a customer a new promise time. Do not invent evidence so Jev has something to say. 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 eval set should include thin-evidence cases, not only happy exception note + SLA bandss. Label exception gold from dispatchers, sla-risk gold, and whether escalate was justified. 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 evidence live in the question text? Put facts in state and point instructions at note.text, playbook.redeliver, sla.priority. Criteria stay stable so you can replay.

When do I split calls? Exception + disruption + sla_risk in one call per stop. Re-optimization is a TMS job after you choose a play.

Where is the rest of the Logistics pack? Start with Logistics input contracts 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.