The OEM-approved signal source and validity policy remain authoritative; normalized values retain source, unit, sample time and validity.
AutoBuild your programIF-01 · Vehicle interface
Vehicle signal observation
Qualify speed, ignition, gear, odometer, energy, SoC, charging and diagnostic observations before any consuming product uses them.
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.
Invalid, stale, out-of-range or unavailable signals remain explicit and cannot be replaced with a plausible default.
No signal observation implies vehicle condition, diagnosis, command execution or physical outcome.
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-04In-dash Navitainment & IVIHardware systemFW-03Vehicle Signal AbstractionEmbedded softwareversioned→fail-closed
Consumers
FW-01Location RuntimeEmbedded softwareFW-02Navigation RuntimeEmbedded softwareFW-04Connectivity & Telemetry AgentEmbedded softwareFW-07eHorizon & ADAS Map RuntimeEmbedded softwareSAAS-01Connected Vehicle CloudSaaS & cloudSAAS-05EV Journey & Charging CloudSaaS & cloudAPP-01Embedded NavigationNative applicationAPP-03EV Cockpit & CompanionNative applicationTransport allocation
Choose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
CAN/CAN-FD/LIN/EthernetOEM vehicle service APIVersioned replay fixture
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 Vehicle signal observation contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.