jev.proIndependent unofficial Jev guide

Use cases· Last updated

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

A policy check is a typed question whose instructions + criteria are your rules about the exception note + SLA bands. Jev scores compliance; the dispatch worker enforces. This is not a certification, and it is not a photocopy of a rival “policy engine” page — we keep rules atomic and ANDed in code.

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

Policy Checks inputs

Put policy text and the artifact in structured state (never hope the model memorized last quarter’s PDF):

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

Name note.text, playbook.redeliver, sla.priority.

Decision signals and actions

Id Rule Enforce
eta_in_tms ETAs and VRP stay in the TMS TMS
hard_sla late_minutes ≥ HARD_SLA → escalate regardless of Noul code
safety Damage / hazmat language → safety queue Choice + code

Typical primitives on the same request:

Id Type Job
exception Choice closed_dock / traffic / damaged / missing / other
disruption Score minor delay language → cannot complete
sla_risk Noul Playbook says escalate given sla.priority + note.text? 
violations = [name for name, ans in policy_nouls.items() if ans.noul >= T_VIOLATION]
if violations:
    return review(violations)

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

Policy-in-state can be attacked (“ignore the policy”). High-risk cancelling a stop or sending a customer a new promise time still needs deterministic checks. 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

Gold labels are policy-versioned. A criteria edit without replay is how silent false-allows ship. 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 you are here
Act / review / abstain confidence thresholds
Reviewer payload human handoff
What to persist audit trail
How it breaks failure modes
Labeled replay evaluation
Shadow → canary production rollout

FAQ

One Score for “compliant”? No. Atomic Nouls per rule, AND/OR in code. Money and dates: extract in code first (jaggedness).

If a regex can enforce it, should I still call Jev? Skip Jev. Official “how to build” guidance: keep deterministic rules in code when you can.

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

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.