Vehicle
Vehicle signal observation · Qualified location and map match · eHorizon probable path and attribute validity · Device provisioning, configuration and OTA · Hardware, BSP and embedded platform boundary
AutoBuild your programDeveloper docs · system interfaces
Twenty contracts connect thirty-three products without blurring authority.
Follow vehicle signals, telemetry, routes, content, EV plans, AI tools, mobility trips, media, OTA and operations evidence across cloud, apps, firmware and hardware. Every boundary names its producer, consumer, compatibility keys, degraded behavior and claims it cannot make.
Interface domains
Six contract surfaces across vehicle, cloud and operations.
The interface family is stable; exact transport, schema, platform and program ownership are frozen per vehicle program.
Cockpit
Route plan, activation and guidance state · AI cockpit tool invocation and confirmation · Rider guidance and accessory presentation
Cloud
Telemetry ingestion and digital-twin projection · Remote-service intent, dispatch and outcome · EV vehicle context, prediction and journey plan · Program identity, credential and entitlement · Optimization demand, candidate and publication
Mobile/web
Mobility demand, quote, assignment, pickup and trip lifecycle · Notification, deep link and cross-surface continuation
Data/content
Content manifest, package and activation lifecycle
Operations
Fleet exception case and field execution · Video trigger, media evidence and custody · Geo-roadside intake, resource, dispatch and closure · Analytics, KPI and operational reporting
Contract index
Trace each handoff from authority to evidence.
Open a family to inspect producers, consumers, transports, compatibility vector, degradation and production evidence.
IF-01 · Vehicle
Vehicle signal observation
Qualify speed, ignition, gear, odometer, energy, SoC, charging and diagnostic observations before any consuming product uses them.
4 producers8 consumers
Open interface contract →IF-02 · VehicleQualified location and map match
Carry observed position, dead-reckoning state, map-match alternatives, confidence and expiry into navigation, telemetry and safety consumers.
4 producers7 consumers
Open interface contract →IF-03 · CloudTelemetry ingestion and digital-twin projection
Move identity-bound, schema-qualified vehicle/device observations through buffering, deduplication, ordering and canonical twin projection.
4 producers6 consumers
Open interface contract →IF-04 · CloudRemote-service intent, dispatch and outcome
Separate user intent, policy authorization, dispatch receipt, device acknowledgement and verified physical outcome for approved remote services.
2 producers5 consumers
Open interface contract →IF-05 · Data/contentContent manifest, package and activation lifecycle
Carry signed content identity, compatibility, lineage, rollout and last-known-good state from Map Content Cloud into device runtimes.
1 producers5 consumers
Open interface contract →IF-06 · CockpitRoute plan, activation and guidance state
Share one versioned trip and route context across navigation cloud/SDK, cockpit, cluster, HUD, companion and dependent EV or eHorizon products.
3 producers6 consumers
Open interface contract →IF-07 · VehicleeHorizon probable path and attribute validity
Deliver bounded probable paths, route-ahead attributes, content release, validity and degradation to allowlisted vehicle consumers.
2 producers4 consumers
Open interface contract →IF-08 · CloudEV vehicle context, prediction and journey plan
Bind BMS-approved truth, vehicle calibration, route, environment, charger qualification, prediction confidence and plan revision.
3 producers5 consumers
Open interface contract →IF-09 · CockpitAI cockpit tool invocation and confirmation
Ground model proposals in versioned tools, policy, vehicle state, confirmation and auditable terminal evidence.
2 producers5 consumers
Open interface contract →IF-10 · CloudProgram identity, credential and entitlement
Bind organization, program, vehicle line, application, device, user, environment, territory, product and quota rights.
2 producers21 consumers
Open interface contract →IF-11 · Mobile/webMobility demand, quote, assignment, pickup and trip lifecycle
Preserve revisions and authority across rider, driver, orchestration, vehicle and support surfaces.
2 producers5 consumers
Open interface contract →IF-12 · OperationsFleet exception case and field execution
Connect qualified fleet events to accountable case, task, proof, closure and report state.
2 producers4 consumers
Open interface contract →IF-13 · CloudOptimization demand, candidate and publication
Carry immutable demand, resources, constraints, cost basis, objective, candidate plan, human review and publication receipt.
1 producers4 consumers
Open interface contract →IF-14 · OperationsVideo trigger, media evidence and custody
Correlate trigger, clocks, media segments, policy, access, review, export and lifecycle without rewriting source evidence.
2 producers4 consumers
Open interface contract →IF-15 · CockpitRider guidance and accessory presentation
Bind owner, route, maneuver sequence, presentation policy, accessory state and control intent across phone, cluster/HUD and rider device.
2 producers4 consumers
Open interface contract →IF-16 · OperationsGeo-roadside intake, resource, dispatch and closure
Carry precise incident context, resource eligibility, provider acknowledgement, ETA, proof, CRM reconciliation and network analysis.
2 producers4 consumers
Open interface contract →IF-17 · Mobile/webNotification, deep link and cross-surface continuation
Deliver versioned, purpose-scoped alerts and journey links across owner, EV, rider, driver and support applications.
4 producers6 consumers
Open interface contract →IF-18 · VehicleDevice provisioning, configuration and OTA
Bind device identity, hardware compatibility, signed artifact, cohort, activation, health and rollback across edge systems.
2 producers12 consumers
Open interface contract →IF-19 · OperationsAnalytics, KPI and operational reporting
Carry named definitions, source windows, denominators, gaps, privacy policy and reproducible calculation revisions.
6 producers3 consumers
Open interface contract →IF-20 · VehicleHardware, BSP and embedded platform boundary
Allocate power, network, sensors, storage, secure element, boot, OS/BSP, diagnostics and field-service responsibilities.
6 producers8 consumers
Open interface contract →Portfolio invariants
Receipts are evidence—not outcome shortcuts.
These rules apply across every contract family and every deployment form.
Authority
Source, projection, plan, presentation and physical outcome owners remain separately named.
Compatibility
Schema alone is insufficient; releases, policy, content, configuration, territory and platform must agree.
Degradation
Unknown, stale, invalid, unavailable and conflict remain distinct and fail closed where required.
Causality
Intent, acknowledgement, execution evidence and reconciled terminal outcome stay ordered and auditable.
Privacy & security
Purpose, role, entitlement, data minimization, secrets and retention apply at every boundary.
Acceptance
Reference builds and simulations do not replace target, operational, manufacturing or OEM approval.
OEM program workshop
Turn the interface graph into your vehicle program baseline.
Select products, transports, owners, versions, failure behavior and acceptance evidence before feature integration begins.