Every calibration claim needs a verifiable trail.

When ADAS is involved in a claim or safety audit, "we calibrated it" is not enough. NADIR produces Evidence Vehicle Bundles (EVB) — signed JSON documents with timestamped drift timelines, validation residuals, sensor graphs, and cryptographic chain of custody from ingest through export.

Download sample EVB API reference Custody brief (MD)

Custody pipeline

Seven stages — each produces an auditable artifact.

1 · IngestTelemetry frames + receipt ID

2 · AlignTemporal sync metadata

3 · ScoreTier + confidence

4 · ChangepointBOCPD / HSMM event

5 · ValidatePost-repair residual

6 · SignEd25519 signature

7 · ExportEVB JSON download

Shadow mode scores continuously; evidence export typically occurs at calibration validation or MSO repair close. No stage modifies vehicle ECU state without explicit customer amendment.

EVB structure

Canonical JSON — sorted keys, hashed, signed.

{
  "bundle_id": "EVB-20260603-B7F2",
  "vehicle_id": "FLEET-204",
  "org_id": "org-nadir-pilot",
  "tier_timeline": [
    { "at": "2026-06-03T14:22:01Z", "tier": "CRITICAL", "confidence": 0.87 },
    { "at": "2026-06-03T15:04:12Z", "tier": "NOMINAL", "confidence": 0.93 }
  ],
  "validation": {
    "residual_deg": 0.07,
    "passed": true,
    "procedure_id": "cal-proc-van-fwd-cam-01"
  },
  "sensor_graph": ["forward_camera", "front_radar", "fusion"],
  "payload_hash": "sha256:8f3a…c21e",
  "signature": "ed25519:7b2c…9f01",
  "signing_key_id": "nadir-evidence-v1",
  "exported_at": "2026-06-03T15:04:18Z"
}

Illustrative structure — field names match API contracts. Full brief: chain-of-custody-brief.md

Who relies on EVBs

Fleet, insurer, MSO, OEM — same bundle, different questions.

Stakeholder	Question	EVB answers
Fleet safety	Was ADAS calibrated before the incident?	Validation block + tier timeline ending NOMINAL before event timestamp
Insurer / DRP	Is subrogation evidence tamper-evident?	Ed25519 signature over canonical payload hash
MSO QA	Did we release with documented calibration health?	Work-order-linked export at structural release
OEM auditor	Traceability for validation program?	Ingest receipt → changepoint → validation chain

Verification steps

How compliance teams validate a bundle.

Download EVB From HORIZON Evidence Theater, Console, or GET /v1/evidence/bundles/{id}.
Canonicalize JSON Sort object keys recursively; compute SHA-256 — must match payload_hash.
Verify signature Ed25519 verify using signing_key_id public key from NADIR trust doc.
Cross-check telematics Align vehicle_id and tier transition timestamps with customer export.
Archive Store bundle + verification log alongside claim or work order record.

API & product links

Integrate evidence export into your workflow.

REST API

POST /v1/evidence/export · GET /v1/evidence/bundles/{id}

API docs →

HORIZON Theater

One-click download from factor graph UI — investor demo ready.

Open Theater →

MSO at close

Attach EVB to work order — Safelite glass · Caliber collision.

MSO solution →

FAQ

Is NADIR automotive safety-certified?

NADIR operates in shadow mode for pilots. Evidence bundles support audit workflows; they do not replace OEM homologation or regulatory certification. See terms.

Where are signing keys stored?

Production keys in HSM-backed signing service. Key rotation documented in security pack — /security.

Difference vs /evidence product page?

/evidence covers product capabilities. This page explains custody mechanics for due diligence and insurer technical review.

See custody end-to-end in 3 minutes

Evidence Theater → download EVB → verify signature block in brief.

Evidence Theater Product overview