Resources

A clear operating language for the handoff.

Use the public product map and security boundaries to align the people who create, verify, and receive high-value freight.

Capability map

How this part of Freight Passport is structured.

Review the authorization workflow →
01

Start with the decision

Review a valid handoff, a mismatch, a protected change, and a replay attempt through the authorization workflow.

  • No production APIs
  • No customer PII
  • Explicit advisory-only outcomes
02

Map one pilot workflow

Bring one facility, one customer decision, and the evidence already used by the current pickup process.

  • Named people and scopes
  • Customer-defined controls
  • Existing release process remains authoritative
03

Review the security boundary

Read how tenant isolation, least privilege, evidence provenance, and fail-closed behavior shape the product.

  • Security and trust page
  • No raw biometric templates
  • No unearned certification claims
04

Keep your systems

Integration categories describe where evidence may come from without implying a live provider connector or partnership.

  • TMS and WMS
  • Carrier and driver identity
  • Facility and movement signals

See it in context

Ready to discuss one handoff?

Request a controlled SHADOW pilot conversation. The intake opens an owner-controlled email path and does not collect shipment or identity evidence on this site.