The signed source observation is authoritative for what was measured; the connected cloud owns the freshness-qualified projection.
AutoBuild your programIF-03 · Cloud interface
Telemetry ingestion and digital-twin projection
Move identity-bound, schema-qualified vehicle/device observations through buffering, deduplication, ordering and canonical twin projection.
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.
Duplicates project once, gaps remain visible, late evidence cannot overwrite newer truth and incompatible schemas quarantine.
Ingestion acceptance does not imply a live vehicle, complete trip, driver behavior, service need or remote 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.
Transport allocation
Choose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
MQTT or HTTPS ingestionVersioned event streamStore-and-forward journal
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 Telemetry ingestion and digital-twin projection contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.