Authoritative map, route, vehicle and service tools own facts and actions; the model may propose but never become source authority.
AutoBuild your programIF-09 · Cockpit interface
AI cockpit tool invocation and confirmation
Ground model proposals in versioned tools, policy, vehicle state, confirmation and auditable terminal evidence.
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.
Unavailable model or tool uses an explicit local fallback; prohibited or stale actions fail before invocation.
Model text, a confirmation receipt or a tool call does not imply vehicle, partner, payment or human 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.
Producers
APP-04AI Cockpit AssistantNative applicationSAAS-09AI Cockpit Orchestration CloudSaaS & cloudversioned→fail-closed
Transport allocation
Choose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
Typed tool SDKCockpit intent APIConfirmation receipt event
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 AI cockpit tool invocation and confirmation contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.