VELARU MANDATE EXHIBIT PACK — MARITIME ROUTING AI
Jurisdiction: Canada (ca)
Modality: Text / Chat
Program: Velaru Maritime Routing AI · Canada (galactic_maritime_routing_ca)
Product ID: maritime_routing:ca:bundle:text
Vertical: maritime_routing
Generated: 2026-08-24T00:23:29.709482Z
Authority: Canada OSFI E-23 Pack — Maritime Routing AI External Validation Pack
Deadline: AIDA (pending) + OSFI E-23 model risk
Velaru verify: https://velaru-erra.onrender.com/verify

EXHIBIT A — AI INVENTORY
[]

EXHIBIT B — GOVERNANCE FRAMEWORK
{
  "framework": "Velaru Mandate Registry \u2014 Maritime Routing AI",
  "exhibit_authority": "Canada OSFI E-23 Pack \u2014 Maritime Routing AI External Validation Pack",
  "regulatory_frameworks": [
    "NERC CIP",
    "REMIT",
    "EU NIS2",
    "AIDA proposal",
    "OSFI E-23",
    "PIPEDA",
    "Quebec Law 25"
  ],
  "standards_alignment": [
    "POSS-2",
    "DRP-1",
    "TCB",
    "FRE 707 pre-compliance",
    "ISO 42001"
  ],
  "human_oversight": "execute Maritime Routing 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 Maritime Routing AI deployer owns AI harm \u2014 vertical SaaS vendor owns liability cap. \u00b7 Quebec Law 25 already strict on automated decisions \u2014 ROC catching up with AIDA.",
  "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": "Maritime Routing AI \u2014 AI decision audit trail required for liability defense",
  "global_leaders_addressed": [
    "Sector regulators",
    "Vertical SaaS platforms",
    "OSFI",
    "RBC",
    "OPC",
    "AMF Quebec"
  ]
}

MIRROR TRAP (regulatory insight)
Niche Maritime Routing AI deployer owns AI harm — vertical SaaS vendor owns liability cap. · Quebec Law 25 already strict on automated decisions — ROC catching up with AIDA.

NERVE CARDS — WHY GLOBAL LEADERS CARE
[
  {
    "title": "Niche litigation",
    "body": "Maritime Routing AI plaintiffs challenge AI decision without independent verify.",
    "source": "vertical"
  },
  {
    "title": "Insurance bind",
    "body": "Sector insurers asking AI governance questions on Maritime Routing AI accounts.",
    "source": "vertical"
  },
  {
    "title": "[Canada] OSFI banks",
    "body": "Canadian bank AI \u2014 E-23 model risk parallels SR 11-7.",
    "source": "jurisdiction"
  },
  {
    "title": "[Canada] Bill C-27",
    "body": "AIDA when passed \u2014 early receipt infrastructure = compliance head start.",
    "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 Maritime Routing AI market
INSURANCE LINES: E&O, Cyber, Sector liability

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