The signed artifact and policy define eligibility; each device owns installed slot and health; the control plane owns observed rollout population.
AutoBuild your programIF-18 · Vehicle interface
Device provisioning, configuration and OTA
Bind device identity, hardware compatibility, signed artifact, cohort, activation, health and rollback across edge systems.
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.
Signature, compatibility, storage, power or health failure stops or rolls back within last-known-good policy.
Offer, download, install, reboot and healthy operation remain separate; cloud state cannot claim physical device success without evidence.
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-10Automotive Developer & Entitlement CloudSaaS & cloudFW-06Device Lifecycle & OTA AgentEmbedded softwareversioned→fail-closed
Consumers
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 systemFW-01Location RuntimeEmbedded softwareFW-02Navigation RuntimeEmbedded softwareFW-03Vehicle Signal AbstractionEmbedded softwareFW-04Connectivity & Telemetry AgentEmbedded softwareFW-05Content & Map Update ManagerEmbedded softwareFW-07eHorizon & ADAS Map RuntimeEmbedded softwareTransport allocation
Choose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
Provisioning APISigned manifestArtifact deliveryBootloader/OS activation adapterHealth report
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 Device provisioning, configuration and OTA contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.