The navigation runtime owns active route and maneuver sequence; displays own presentation receipts, not route truth.
AutoBuild your programIF-06 · Cockpit interface
Route plan, activation and guidance state
Share one versioned trip and route context across navigation cloud/SDK, cockpit, cluster, HUD, companion and dependent EV or eHorizon products.
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.
Position ambiguity, stale traffic, incompatible content or secondary-display loss preserve route lineage and expose degradation.
A guidance state does not prove display, audio delivery, maneuver execution, arrival or driver compliance.
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.
Transport allocation
Choose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
Navigation SDK APIStable runtime IPCCluster/HUD presentation contractDeep-link handoff
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 Route plan, activation and guidance state contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.