versioned test definition and acceptance threshold
Positioning and map matching
Prove bounded location qualification and recovery without inventing road or lane certainty.
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
urban canyon
- 02
tunnel entry, dwell and exit
- 03
flyover overlap and stacked roads
- 04
weak and lost GNSS
- 05
dead-reckoning expiry
- 06
cold and warm start
- 07
map-match ambiguity
- 08
sequence gap and late observation
- 09
recovery after signal return
- 10
cross-runtime timestamp and unit consistency
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.
Verify behavior at the handoff, not only inside the component.
Open each contract to freeze authority, compatibility, degradation and prohibited outcome claims.
Vehicle signal observation
Invalid, stale, out-of-range or unavailable signals remain explicit and cannot be replaced with a plausible default.
Open contract →IF-02 · VehicleQualified 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-03 · CloudTelemetry ingestion and digital-twin projection
Duplicates project once, gaps remain visible, late evidence cannot overwrite newer truth and incompatible schemas quarantine.
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 →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
Plan positioning and map matching evidence for the exact vehicle.
Allocate scenarios, targets, versions, fixtures, thresholds, review and acceptance before declaring readiness.