The eHorizon runtime owns a qualified map-derived output; consumer ECUs retain complete function and safety authority.
AutoBuild your programIF-07 · Vehicle interface
eHorizon probable path and attribute validity
Deliver bounded probable paths, route-ahead attributes, content release, validity and degradation to allowlisted vehicle consumers.
Authority model
Name the source—and name what it cannot prove.
The same message can be observation, projection, plan, receipt or physical evidence. This contract keeps those meanings separate.
Low localization, stale content, ambiguous ramp, unsupported consumer or coverage gap publishes degraded or unavailable state.
Map-as-a-sensor output never implies steering, braking, speed control, lighting actuation or production safety acceptance.
Product allocation
Producer and consumer responsibilities are explicit.
A product can appear on both sides when it transforms one authority into another; each transformation retains its own evidence.
Producers
SAAS-06eHorizon & HD Map CloudSaaS & cloudFW-07eHorizon & ADAS Map RuntimeEmbedded softwareversioned→fail-closed
Transport allocation
Choose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
ADASIS v2/v3 profileStable embedded APINDS or OEM-agreed content
Compatibility vector
- schema or ABI version
- producer release
- consumer release
- policy and entitlement revision
- content/configuration revision
- territory/platform profile
Acceptance evidence
- contract compatibility
- nominal and negative scenarios
- ordering, replay and idempotency
- latency, capacity and resource bounds
- security, privacy and role enforcement
- offline, recovery and rollback
- target or operational acceptance
OEM program workshop
Freeze the eHorizon probable path and attribute validity contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.