Navigation owns route and maneuver truth; the accessory owns power/thermal/capability state; presentation remains a scoped receipt.
AutoBuild your programIF-15 · Cockpit interface
Rider guidance and accessory presentation
Bind owner, route, maneuver sequence, presentation policy, accessory state and control intent across phone, cluster/HUD and rider device.
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.
Phone loss, route mismatch, expired maneuver, low battery, thermal protection or pairing mismatch disables affected presentation.
Eligible guidance does not prove photons, audio, rider attention, maneuver execution or emergency dispatch.
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.
BLE or accessory linkCluster/HUD adapterPresentation receiptControl intent API
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 Rider guidance and accessory presentation contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.