versioned test definition and acceptance threshold
AutoBuild your programVER-01 · OEM verification domain
Search and destination entry
Prove India-aware destination success without promoting ambiguity or moving-state input into a false match.
Scenario matrix
Ten paths—including ambiguity, loss, replay and recovery.
The vehicle program turns each scenario into versioned test cases with routes, fixtures, conditions, thresholds and accountable verdicts.
- 01
misspellings and fuzzy intent
- 02
phonetics and vernacular input
- 03
landmark, house and entrance precision
- 04
ambiguous names and duplicate places
- 05
Mappls PIN/eLoc resolution
- 06
service, charger and dealer discovery
- 07
nearby and along-route context
- 08
moving-vehicle input restrictions
- 09
offline and unavailable search
- 10
confidence, no-result and correction flow
Product allocation
Every participant retains its own authority and release evidence.
Green results in one participant do not promote another product—or a physical outcome—to accepted.
Interface allocation
Verify behavior at the handoff, not only inside the component.
Open each contract to freeze authority, compatibility, degradation and prohibited outcome claims.
IF-05 · Data/content
Content manifest, package and activation lifecycle
Interrupted download resumes safely, signature or compatibility failure blocks staging, and failed health returns to last known good.
Open contract →IF-06 · CockpitRoute plan, activation and guidance state
Position ambiguity, stale traffic, incompatible content or secondary-display loss preserve route lineage and expose degradation.
Open contract →IF-09 · CockpitAI cockpit tool invocation and confirmation
Unavailable model or tool uses an explicit local fallback; prohibited or stale actions fail before invocation.
Open contract →IF-16 · OperationsGeo-roadside intake, resource, dispatch and closure
Ambiguous location pauses recommendation, no eligible resource escalates, provider decline remains unassigned and incomplete proof blocks closure.
Open contract →Evidence package
A verdict stays reproducible, attributable and reviewable.
These fields travel together so a screenshot or summary cannot become disconnected from its exact conditions.
fixture, route, data and environment provenance
raw result plus summarized verdict
defect, deviation and retest disposition
product, schema, content, policy and configuration versions
independent review and accountable approval
target, laboratory, vehicle or operational evidence where required
OEM program workshop
Plan search and destination entry evidence for the exact vehicle.
Allocate scenarios, targets, versions, fixtures, thresholds, review and acceptance before declaring readiness.