Phone/embedded navigation
Route authority
OwnsActive route revision and ordered maneuvers
Must not inferAccessory sensor proposal cannot invent maneuver
AutoBuild your programPublic reference architecture
Two-wheeler Rider Guidance
Glanceable guidance that never outlives its route, owner, power or safety evidence.
Bind every presentation to current ownership, pairing, route revision, maneuver sequence, power/thermal state and device capability across cluster, HUD and accessory surfaces.
Authority by layer
Know which component owns the state—and what it must never infer.
Every layer exposes an authoritative responsibility and an explicit non-authority boundary.
Companion/device identity
Pairing and ownership
OwnsCurrent owner, visible code and session capability
Must not inferPrior owner or code alone cannot pair
FW-02/FW-06
Guidance runtime
OwnsEligibility, sequence, expiry, power and thermal gating
Must not inferPresentation record is not physical output
HW-05/HW-06
Rider surfaces
OwnsAllowlisted controls and declared visual/tactile capability
Must not inferSunlight layout is not a readability or safety claim
End-to-end operating flow
State advances through evidence—not optimistic UI.
Each transition names both the action and the identity or version evidence that makes it reproducible.
- 01
Pair
Validate current owner, visible code, device state and capability.
owner/device/session · code expiry · policy - 02
Receive maneuver
Bind exact route, sequence, expiry and content/runtime versions.
route revision · maneuver ID · sequence - 03
Qualify device
Check phone presence, battery, thermal, display and declared output capability.
health/config · observed time · capability - 04
Present
Choose permitted layout and record reference presentation without physical claim.
presentation revision · layout · false output boundary - 05
Control/lifecycle
Accept allowlisted debounced controls; update via health-gated rollback lifecycle.
control/idempotency · release/config · health
Contract families
Interfaces that a production program must own.
Pairing
Owner/device/code/session/capability and revocation.
Guidance
Route, maneuver, sequence, expiry, versions and validity.
Presentation/control
Surface layout, capability, revision and allowlisted intents.
Lifecycle
Config/release, preflight, health, commit and rollback.
Designed degradation
Failure states stay truthful and useful.
Phone lost / maneuver expired
Make every presentation unavailable rather than repeat stale guidance.
Route mismatch / sequence gap
Fail separately and hold presentation until authoritative recovery.
Low battery / thermal
Protect accessory independently and declare reduced/unavailable capability.
Glove/button bounce
Suppress duplicate control without changing route state.
Security & privacy controls
Privilege follows the narrowest useful boundary.
- ✓Current-owner proof and revocable pairing
- ✓Minimum route/maneuver payload to accessory
- ✓Control allowlist, revision and debounce
- ✓Signed release/config with health-gated commit
- ✓No emergency, readability or physical-presentation claim without target evidence
Release evidence
A green demo is not a production acceptance case.
- 01Owner transfer, pairing expiry and phone-loss tests
- 02Route/sequence/expiry and off-route behavior
- 03Sunlight/glove/vibration target HMI validation
- 04Battery/thermal/environmental and acoustic capability
- 05Lifecycle preflight, power loss, health and rollback
Independently scopeable products
Compose the system without collapsing product ownership.
Each product can be bought and operated independently while sharing identity, context and lifecycle contracts.
OEM program workshop
Turn the Two-wheeler Rider Guidance reference into your program architecture.
Confirm target products, vehicle and cloud boundaries, source systems, contract versions, deployment, validation and lifecycle ownership.