One authority per state
Vehicle signal, route, plan, case, tool, credential and partner outcome each retain a declared owner.
AutoBuild your programPublic program architectures
See where every truth lives—and what happens when a dependency does not.
These product-system views connect cloud, native application, embedded runtime, firmware and hardware boundaries. They help OEM teams evaluate authority, contracts, degraded behavior, security and release evidence before program scope.
Architecture method
Begin with authority. Design the failure path. Attach every claim to evidence.
A module list is not an operating architecture. Each view makes source of truth, non-authority, identity, revision, degradation and acceptance evidence visible.
Client intent stays intent
Apps may queue or project pending work, but only authoritative acknowledgement advances canonical state.
Degradation is designed
Offline, stale, ambiguous, incompatible, denied and uncertain are product states—not hidden errors.
Fourteen product systems
Follow a complete operating loop from evidence source to release gate.
Open a system to inspect layers, authority, end-to-end flow, contract families, security controls, degraded behavior and program evidence.
CV01 · Cloud · companion · TCU
Connected Vehicle System
One freshness-aware vehicle truth from edge evidence to owner experience.
- Products
- 4
- Layers
- 4
- Release gates
- 5
EN02 · IVI · runtime · vehicle signals
Embedded Navigation
One authoritative route across IVI, cluster, HUD and degraded operation.
- Products
- 5
- Layers
- 4
- Release gates
- 5
EV03 · BMS · energy cloud · cockpit
EV Journey & Charging
Keep vehicle energy truth, prediction and charging-network evidence visibly separate.
- Products
- 3
- Layers
- 4
- Release gates
- 5
CI04 · Journey demand · assets · field operations
Charging Intelligence Operations
Route-aware charging evidence from source-qualified asset state to explainable network action.
- Products
- 4
- Layers
- 4
- Release gates
- 5
FT05 · Live fleet · operator · driver · tracker
Fleet Control & Execution
An exception-led operating picture with accountable state and proof-gated closure.
- Products
- 4
- Layers
- 4
- Release gates
- 5
RN06 · Demand · constraints · execution
RouteNet Optimization
A reproducible plan whose trade-offs and unassigned work remain explainable.
- Products
- 3
- Layers
- 4
- Release gates
- 5
MC07 · Release · delivery · edge activation
Map Content Lifecycle
Downloaded, verified, staged and active remain separate population truths.
- Products
- 3
- Layers
- 4
- Release gates
- 5
AI08 · Model · typed tools · deterministic HMI
Governed AI Cockpit
Natural conversation with deterministic automotive authority.
- Products
- 4
- Layers
- 4
- Release gates
- 5
DX09 · Entitlement · identity · conformance
Developer Cloud & Console
From product discovery to production evidence without credential sprawl.
- Products
- 2
- Layers
- 4
- Release gates
- 5
SM10 · Quote · assignment · pickup · trip
Mobility Orchestration & Rider
A truthful mobility promise from precise pickup to completed trip.
- Products
- 3
- Layers
- 4
- Release gates
- 5
EH11 · HD content · probable path · edge profile
eHorizon & ADAS Map
Qualified road-ahead context with explicit validity and safe withdrawal.
- Products
- 3
- Layers
- 4
- Release gates
- 5
GO12 · Private layers · dispatch · field proof
Geo Operations & Roadside
Precise intake and eligible-resource evidence before dispatch or closure.
- Products
- 3
- Layers
- 4
- Release gates
- 5
VE13 · Camera · event evidence · human review
Video Telematics Evidence
Preserve trigger, clocks, media policy and custody without turning inference into fact.
- Products
- 4
- Layers
- 4
- Release gates
- 5
RG14 · Phone · cluster/HUD · accessory
Two-wheeler Rider Guidance
Glanceable guidance that never outlives its route, owner, power or safety evidence.
- Products
- 4
- Layers
- 4
- Release gates
- 5
Use in OEM discovery
Turn a reference view into a program-specific responsibility matrix.
The selected vehicle, territory, platform, deployment and lifecycle determine the final interfaces and assurance owners.
Scope
Choose products, users, vehicle lines, territories, surfaces and outcome measures.
Allocate
Assign every source, state, adapter, policy, failure and operational owner.
Contract
Freeze versioned schemas, timing, identity, rights, compatibility and rollback behavior.
Prove
Attach test, simulator, HIL, vehicle, security, privacy and operational evidence to release.
OEM program workshop
Bring the target vehicle and program boundary.
Use these public reference architectures to start an OEM workshop, then bind exact products, interfaces, deployment, safety/security responsibilities and lifecycle evidence.