Compliance

Compliance is structural, not a checkbox.

Per-state rule sets versioned in YAML. A tamper-evident audit trail across every shipment. The compliance engine gates every meaningful operational action against the rules version active at that moment.

— RULE SETS

Versioned by state. Updated as the law moves.

Each state we operate in carries its own YAML rules file. Insurance minimums, required documents, transit windows, operational standards — every meaningful constraint lives in the rule set and gets gated by the compliance engine.

Florida

v4.2.1

IRS-style multi-factor test. Active since 2026.

Texas

v3.8.0

TWC 20-factor + HB 100 marketplace protections.

Minnesota

v2.1.4

Minn. Stat. § 176.043 7-factor courier statute.

Expanding

On demand

We expand into states as client demand justifies it.

— PILLARS

How the compliance posture holds.

01 — Rule sets

YAML, not memory

Operational rules per state are versioned text files. Insurance minimums, document requirements, release windows, operating-standard exceptions — all reviewed, all dated, all diffable.

02 — Audit trail

append-only and hash-chained

Every meaningful operational event writes an entry. Entries are hash-chained — tamper-evident. We can export a complete shipment history in court-admissible format in under 60 seconds.

03 — Gating

the engine, not the team, says no

The compliance engine gates every meaningful action against the rules version active at that moment. If a state's insurance minimum changes Tuesday, the gate updates Wednesday — no manual sync.

04 — Documents

OCR-verified, not "trust us"

Insurance certificates and similar documents go through OCR + manual verification before they are accepted. The audit log captures verification confidence and reviewer identity.

Want the longer version?

Talk to us about how the compliance engine maps to your operations.