01
Current inputs
The evaluator uses server-assembled state rather than trusting facts supplied by a browser or bearer.
- Assignments and facility scope
- Current evidence and expiry
- Exact published policy
ReleaseLock
Verify the pickup authority, not just the pickup number.
ReleaseLock assembles the current load, carrier, driver, equipment, facility, destination, evidence, and policy into one customer-facing custody decision.
Capability map
How this part of Freight Passport is structured.
02
Clear outcomes
Operators receive explicit status language and reason codes without relying on color alone.
- Policy controls satisfied
- Security Review required
- Do not release
03
Customer remains in control
A satisfied policy result still requires the customer’s release decision before a credential is issued.
- No force-green shortcut
- Separate decision evidence
- Current-state revalidation
04
Bound credential
The release credential is short-lived, one-use, and bound to the exact decision, load, facility, and authorization state.
- No bearer value in logs
- Atomic redemption
- Replay signal on reuse
See it in context
Test the handoff decision yourself.
Use fictional shipment data to explore a valid arrival, a blocked mismatch, a protected change, and a replay attempt.