VELARU MANDATE EXHIBIT PACK — FLEET FMCSA COMPLIANCE AI
Jurisdiction: China (cn)
Modality: Text / Chat
Program: Velaru Fleet FMCSA Compliance AI · China (galactic_fleet_compliance_cn)
Product ID: fleet_compliance:cn:bundle:text
Vertical: fleet_compliance
Generated: 2026-08-23T23:34:34.510562Z
Authority: China CAC Algorithm Filing Pack — Fleet FMCSA Compliance AI External Validation Pack
Deadline: CAC algorithm filing + PIPL
Velaru verify: https://velaru-erra.onrender.com/verify

EXHIBIT A — AI INVENTORY
[]

EXHIBIT B — GOVERNANCE FRAMEWORK
{
  "framework": "Velaru Mandate Registry \u2014 Fleet FMCSA Compliance AI",
  "exhibit_authority": "China CAC Algorithm Filing Pack \u2014 Fleet FMCSA Compliance AI External Validation Pack",
  "regulatory_frameworks": [
    "NHTSA Standing General Order",
    "EU AI Act Annex III",
    "CAC Generative AI Measures",
    "PIPL",
    "DSL",
    "Algorithm Recommendation Rules"
  ],
  "standards_alignment": [
    "POSS-2",
    "DRP-1",
    "TCB",
    "FRE 707 pre-compliance",
    "ISO 42001"
  ],
  "human_oversight": "execute Fleet FMCSA Compliance AI AI decision",
  "third_party_verification": "https://velaru-erra.onrender.com/verify (operator-independent)",
  "data_lineage": "Hash-chained Ed25519 receipts; optional RFC3161 + external anchor",
  "mirror_trap": "Niche Fleet FMCSA Compliance AI deployer owns AI harm \u2014 vertical SaaS vendor owns liability cap. \u00b7 Algorithm filing requires decision logic documentation \u2014 independent verify acceptable to CAC review.",
  "chain_integrity": {
    "depth": 6,
    "invariant_holds": true
  }
}

EXHIBIT D — DATA INPUTS & VALIDATION
{
  "data_validation_method": "Cryptographic receipt per AI decision; public verify without trusting deployer, vendor, or Velaru operator",
  "bias_testing_proxy": "Asymmetry score from live chain signals",
  "model_change_control": "Policy lock registry \u2014 criteria hash frozen pre-dispute",
  "logging_retention": "90-day pre-dispute window minimum; permanent verify permalinks",
  "external_validator": "Nisaba LLC / Velaru",
  "validator_independence": "Client-side Ed25519 verify; BYOK tri-receipt optional",
  "headline_stat": "Fleet FMCSA Compliance AI \u2014 AI decision audit trail required for liability defense",
  "global_leaders_addressed": [
    "Sector regulators",
    "Vertical SaaS platforms",
    "CAC",
    "Tencent",
    "Alibaba",
    "ByteDance"
  ]
}

MIRROR TRAP (regulatory insight)
Niche Fleet FMCSA Compliance AI deployer owns AI harm — vertical SaaS vendor owns liability cap. · Algorithm filing requires decision logic documentation — independent verify acceptable to CAC review.

NERVE CARDS — WHY GLOBAL LEADERS CARE
[
  {
    "title": "Niche litigation",
    "body": "Fleet FMCSA Compliance AI plaintiffs challenge AI decision without independent verify.",
    "source": "vertical"
  },
  {
    "title": "Insurance bind",
    "body": "Sector insurers asking AI governance questions on Fleet FMCSA Compliance AI accounts.",
    "source": "vertical"
  },
  {
    "title": "[China] Dual compliance",
    "body": "Multinationals operating CN + US/EU \u2014 one architecture, jurisdiction-tagged receipts.",
    "source": "jurisdiction"
  },
  {
    "title": "[China] DeepSeek moment",
    "body": "Chinese model deployment globally \u2014 provenance receipt links model to decision.",
    "source": "jurisdiction"
  },
  {
    "title": "[Text / Chat] Modality hook",
    "body": "Baseline \u2014 all frameworks apply to text decisions.",
    "source": "modality"
  }
]

BOOK SUMMARY: {
  "total_insureds": 0,
  "compliant": 0,
  "grace_period": 0,
  "non_compliant": 0,
  "expired": 0,
  "not_enrolled": 0,
  "compliant_pct": 0.0
}

TAM / EXPOSURE: Global Fleet FMCSA Compliance AI market
INSURANCE LINES: E&O, Cyber, Sector liability

DISCLAIMER: External validation evidence pack — not legal advice, not filed rate approval.