versioned test definition and acceptance threshold
AutoBuild your programVER-08 · OEM verification domain
ADAS, eHorizon and HD maps
Prove qualified coverage, probable path, attribute validity and safe degradation inside the OEM safety architecture.
Scenario matrix
Ten paths—including ambiguity, loss, replay and recovery.
The vehicle program turns each scenario into versioned test cases with routes, fixtures, conditions, thresholds and accountable verdicts.
- 01
ODD and corridor coverage
- 02
content and live-map freshness
- 03
localization and horizon error
- 04
false and missing attributes
- 05
ambiguous probable path
- 06
consumer allowlist and schema
- 07
safe degradation
- 08
content rollback
- 09
exact replay and traceability
- 10
assumption-of-use violation
Product allocation
Every participant retains its own authority and release evidence.
Green results in one participant do not promote another product—or a physical outcome—to accepted.
Interface allocation
Verify behavior at the handoff, not only inside the component.
Open each contract to freeze authority, compatibility, degradation and prohibited outcome claims.
IF-02 · Vehicle
Qualified location and map match
Ambiguity, tunnel, sequence gap and expired dead reckoning hold dependent progression instead of inventing a lane or road.
Open contract →IF-05 · Data/contentContent manifest, package and activation lifecycle
Interrupted download resumes safely, signature or compatibility failure blocks staging, and failed health returns to last known good.
Open contract →IF-07 · VehicleeHorizon probable path and attribute validity
Low localization, stale content, ambiguous ramp, unsupported consumer or coverage gap publishes degraded or unavailable state.
Open contract →IF-20 · VehicleHardware, BSP and embedded platform boundary
Absent peripheral, brownout, thermal, storage, clock, network or boot fault enters a bounded degraded state with diagnostics.
Open contract →Evidence package
A verdict stays reproducible, attributable and reviewable.
These fields travel together so a screenshot or summary cannot become disconnected from its exact conditions.
fixture, route, data and environment provenance
raw result plus summarized verdict
defect, deviation and retest disposition
product, schema, content, policy and configuration versions
independent review and accountable approval
target, laboratory, vehicle or operational evidence where required
OEM program workshop
Plan adas, ehorizon and hd maps evidence for the exact vehicle.
Allocate scenarios, targets, versions, fixtures, thresholds, review and acceptance before declaring readiness.