Four systems that assume the data might be lying.

Authority, insurance, safety history, identity chain, and banking are checked before a carrier can be offered a load, then re-checked continuously while the load is moving. Every clearance decision records which source data it used and how old that data was.

• FMCSA authority and safety monitoring with source provenance
• Certificate-of-insurance workflow with OCR-assisted review
• Identity chain: EIN, representative, bank account name, dispatch origin
• Explainable ShieldScore — never a single signal, never an unexplained block

Driver mobile GPS and the carrier ELD stream are read independently and compared. Divergence, staleness, route deviation, and unexpected stops each raise a scored signal rather than an automatic verdict.

• Independent mobile and ELD position streams
• Divergence, freshness, deviation, and motion-correlation signals
• Tracking states from healthy through lockdown-recommended
• Escalation playbooks that put a human on the decision

Shippers, facilities, loads, stops, rates, margin controls, matching, tendering, and settlement — the operational system of record, with the security model built in rather than bolted on.

• Load lifecycle with an enforced state machine
• Margin and approval thresholds in exact integer money
• PostGIS proximity matching with explainable rankings
• Tender cascade, Book-It-Now, and double-cover protection

Every status change, document version, message, and risk decision is written to an append-only, hash-chained ledger. When a claim arrives, the chronology is exportable rather than reconstructed.

• Append-only audit events with hash chaining
• Document versioning, retention, and legal hold
• Reproducible risk decisions with the source snapshot
• One-click evidence package for claims and litigation