Frozen electrical/mechanical design and selected components own physical limits; BSP and firmware expose versioned capability and health.
AutoBuild your programIF-20 · Vehicle interface
Hardware, BSP and embedded platform boundary
Allocate power, network, sensors, storage, secure element, boot, OS/BSP, diagnostics and field-service responsibilities.
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.
Absent peripheral, brownout, thermal, storage, clock, network or boot fault enters a bounded degraded state with diagnostics.
A reference design, host build or simulated interface does not imply a frozen BOM, prototype result, certification, PPAP or SOP 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
HW-01Line-fit TCUHardware systemHW-02AIS-140 / Fleet TrackerHardware systemHW-03Dashcam & Video TelematicsHardware systemHW-04In-dash Navitainment & IVIHardware systemHW-05Two-wheeler Cluster & HUDHardware systemHW-06Rider AccessoryHardware systemversioned→fail-closed
Consumers
FW-01Location RuntimeEmbedded softwareFW-02Navigation RuntimeEmbedded softwareFW-03Vehicle Signal AbstractionEmbedded softwareFW-04Connectivity & Telemetry AgentEmbedded softwareFW-05Content & Map Update ManagerEmbedded softwareFW-06Device Lifecycle & OTA AgentEmbedded softwareFW-07eHorizon & ADAS Map RuntimeEmbedded softwareAPP-01Embedded NavigationNative applicationTransport allocation
Choose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
Board and harness interface controlBSP/driver APISecure boot and key serviceDiagnostics and manufacturing testPower-mode contract
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 Hardware, BSP and embedded platform boundary contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.