Trust Center

Every HazSeal verdict is traceable to an edition, a set of articles and a data manifest. This page explains where the data comes from and what we do when we cannot verify something.

Data provenance

ADR 2025 data extracted from the official UNECE text (ECE/TRANS/352), dual-extraction verified, manifest dbdb64bb.

The engine refuses to load any dataset whose sha256 does not match the pinned manifest, and refuses records not stamped ADR2025 — it fails closed, never open.

edition: ADR2025 · records: 2939 · manifest: dbdb64bb

Fail-closed by design

The ADR 2025 Volume II rules (7.5.2 mixed loading matrices, 8.6.4 tunnel table, 5.3 placarding) are now verified and sealed (rules manifest f3089d9a) — the former NEEDS_REVIEW fallbacks and split-code assumptions were replaced by verbatim-grounded verdicts. Anything still not derivable from the sealed data (e.g. EHS status per 2.2.9.1.10, carriage temperature) is surfaced as an explicit check prompt, never guessed.

Modes and licensing

Road (ADR) is live. Sea (IMDG) and air (ICAO TI / IATA DGR) are visible in the product but disabled: the datasets are not yet licensed, and we do not ship unlicensed or scraped regulatory data.

The edition seal

Every API answer carries { edition: ADR2025, articles, manifest: dbdb64bb, generatedAt } so an auditor can reproduce it against the exact same text.

{
  "result": { ... },
  "basis": {
    "edition": "ADR2025",
    "articles": ["1.1.3.6.3", "1.1.3.6.4"],
    "manifest": "dbdb64bb",
    "generatedAt": "2026-08-01T12:00:00.000Z"
  }
}

Chain Anchor

The Bronze seal ledger is hash-chained: the head (hash of the last record) commits to every byte of every record before it. We periodically publish this head hash — an external immutability anchor. Anyone holding a published head can re-verify that the ledger was not rewritten.

Current head: a4f15edc
Records: 13
Last anchor: No anchor published yet.