Logistics audit trail 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 audit trail slice of the logistics dispatch decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to logistics dispatch decisions audit trail. Primary search language: Logistics Jev audit trail. 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
An audit trail for logistics dispatch decisions is a decision trace: replayable inputs, typed answers, floors, and the play the dispatch worker took. It is not a driver chat log and not a clone of a TMS history screen.
Hub: Use cases. Compare, when the other tool is the real job: logistics dispatch.
Audit Trail inputs
Persist the filtered payload (the contract), not the GPS dump you refused to POST:
{
"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." }
}Redact customer phones and gate codes before the object hits cold storage.
Decision signals and actions
Minimum fields:
- stop id + filtered note
- TMS late minutes + playbook SHA
- model pin + question SHA
- answers + full
probabilitiesmap - play applied (
play:closed_dock,dispatcher_review,escalate_sla, …) - TMS job id after re-optimize (if any)
Argmax-only logs cannot explain a close sla_risk Noul. Also store usage.input_tokens (vendor meter).
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 you cannot explain cancelling a stop or sending a customer a new promise time from the trace, you are not ready to auto-act. 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
Traces are the eval warehouse. Replay against exception gold from dispatchers, sla-risk gold, and whether escalate was justified after criteria or alias changes. 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 | you are here |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is the HTTP log enough? No. Persist the filtered state, full probabilities, floors, and downstream play as a decision trace.
May I log raw customer phones or gate codes? Redact in code. Jev will not be your DLP layer.
Where is the rest of the Logistics pack? Start with Logistics human handoff and Logistics evaluation. 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.