From repair event to signed evidence in five steps.

Shadow mode means NADIR scores telematics, assigns NOMINAL / CAUTION / CRITICAL tiers, and exports signed evidence — without writing calibration parameters to the vehicle.

Your maintenance team decides whether to pull a unit, schedule a bay recalibration, or return it to route. NADIR does not override OEM safety controllers.

This is intentional: post-repair detection pilots should prove alert quality before anyone discusses automation or correction paths.

• Console CRITICAL rows are recommendations, not work orders.
• Weekly digest emails summarize CAUTION trends without paging on-call at 2 a.m.
• Sample EVBs document what the model saw — useful for QA, not a legal verdict.

Actuation

None

Default mode

Shadow

ECU writes

Not supported in pilots

NADIR is not ASIL-certified software and does not replace OEM calibration procedures or static target rigs.

A valid evidence bundle signature proves integrity of the JSON record — not that the windshield camera is physically aligned.

Controlled benchmark figures on this site illustrate detector behavior on seed data; field accuracy requires your own MTTFF-RE readout.

If a vendor implies OEM sign-off from a dashboard alone, ask for the underlying evidence schema and pilot KPI.

After MTTFF-RE meets your SOW threshold, fleets may renew Shadow Ops ($750/mo) or open a regional evaluation ($15k+).

Correction, HORIZON forecasting, and tier upgrades remain internal or design-partner only until three paid shadow pilots complete.

Each expansion adds explicit contract language for data retention, rate limits, and excluded actuation paths.

Pilot exit

Pass / fail / stop

Renewal gate

MTTFF-RE

Correction

Not sold publicly

NADIR provides advisory analytics on exported telematics correlated to repair order close timestamps.

Outputs include tier assignments, reason codes, and optional signed JSON evidence bundles.

Customer retains operational authority over vehicle dispatch and calibration vendor selection.

# SOW boundary snippet (illustrative)
scope:
  mode: shadow_advisory
  ecu_writes: false
  kpi: MTTFF-RE
  actuation: none
deliverables:
  - weekly_digest_csv
  - console_critical_queue
  - sample_evidence_bundles
  - week_4_exhibit_a_chart

The commercial motion is a bounded $750 proof on 50–150 VINs with one KPI — easy for fleet CFOs to approve.

Shadow detection de-risks integration: no ECU access, no bay hardware, no ASIL claims.

Expansion revenue attaches to proven alert quality, not tier shopping in week one.

VIN (17 char), RO identifier, close timestamp (UTC preferred), procedure category, and shop identifier.

Optional but valuable: part numbers for glass, ADAS kit replacement flag, technician notes.

NADIR validates identity before joining — malformed VINs land in a quarantine report, not silent scoring.

Required

vin · ro_id · closed_at · procedure

Format

CSV · JSON · webhook

Cadence

Daily batch minimum

Weekly CSV from MSO export is enough for most $750 proofs.

Webhook on RO close tightens MTTFF-RE measurement when telematics latency is low.

Idempotency keys prevent duplicate events when shops retransmit files.

POST /v1/repair-events
Authorization: Bearer ${NADIR_TOKEN}
Content-Type: application/json

{
  "idempotency_key": "ro-88421-vin-1HGBH41JXMN109186",
  "vin": "1HGBH41JXMN109186",
  "ro_id": "RO-88421",
  "closed_at": "2026-07-15T18:42:00Z",
  "procedure": "windshield_replacement",
  "shop_id": "SAFELITE-DTW-014"
}

Local shop time without timezone — converts incorrectly across DST.

RO marked closed before vehicle actually leaves bay — starts MTTFF clock too early.

Fleet unit numbers instead of VIN — must map through a stable crosswalk table.

Prefer the feed with earliest accurate close timestamp; document precedence in kickoff notes.

Conflicts surface in a reconciliation CSV — not auto-merged without operator ack.

RO payloads retain operational fields only — no customer PII beyond VIN and shop IDs in default pilot tier.

Retention windows defined in order form; export/delete available on request.

A green ADAS dashboard means self-check passed — not that alignment matches factory spec.

When camera lane proxy and radar range-rate disagree for days after glass work, that pattern elevates tier.

Single spikes from weather or harsh braking decay; persistence drives CAUTION and CRITICAL.

Pulse compares observed trajectories to a baseline envelope tuned for post-repair windows.

Outputs: tier, confidence, reason_codes[], model_id, policy_id.

Policies version independently from models — replay uses both IDs.

Tiers

NOMINAL · CAUTION · CRITICAL

Policy

Versioned JSON

Outputs

Reason codes + confidence

Sample CAUTION events with maintenance leads — label true vs nuisance.

Adjust observation window or procedure filters before week four readout.

Goal is actionable CRITICAL rate, not zero CAUTION.

Scoring window opens at RO close — pre-repair baseline excluded from post-RO residual.

Changepoint detectors flag abrupt shifts; sustained elevation drives tier transitions.

Cannot distinguish all root causes (wrong part vs skipped scan vs partial cal).

CRITICAL means inspect — not auto-assign blame to shop or OEM.

Confirm cohort VIN list, RO feed owner, telematics export owner, legal shadow language.

Deliver adapter manifest draft and sample batch template.

Attendees

Maint · IT · Legal optional

Output

Data contract v1

Quarantine report reviewed jointly. Scoring enabled on clean subset.

Maintenance labels true positives vs nuisance. Policy tweaks if agreed.

Verify workflow demo. Digest cadence confirmed.

Pass, fail, or stop with written appendix. Commercial renewal conversation only after pass.