Decision owner
Owner with dealer confirmation
The named role remains accountable for the consequential decision.
Automotive & Mobility
Designed for Vehicle owner
Answer a vehicle owner's questions about their exact VIN configuration, warning lights, and service needs using the owner manual, build configuration, and connected telemetry, with dealer confirmation before any booking or remote command.
Contract AUT-01 · primary aggregate VehicleOwnership · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Owner with dealer confirmation
The named role remains accountable for the consequential decision.
Governed evidence
6 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
1 approval gate
Approval gates prevent the copilot from making consequential decisions.
An owner photographs an amber tyre-pressure light; the companion reads the latest telemetry showing the rear-left tyre at 1.9 bar, cites the trim-specific inflation table from the manual, notes an open suspension recall with parts available, and books the dealer visit only after the owner confirms the proposed Thursday slot..
Answer a vehicle owner's questions about their exact VIN configuration, warning lights, and service needs using the owner manual, build configuration, and connected telemetry, with dealer confirmation before any booking or remote command.
Confirmed booking or executed command with audit record gives Owner with dealer confirmation the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Owner with dealer confirmation verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Vehicle owner performs ask a vehicle question in the app using Question, warning light photo, or voice prompt and produces Intent bound to the owner's VIN. The transition is deterministic and does not require autonomous model approval.
Why it matters: Intent bound to the owner's VIN gives Vehicle identity service the evidence needed to begin Resolve VIN configuration and entitlements, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/ask-a-vehicle-question-in-the-app
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Vehicle identity service performs resolve vin configuration and entitlements using VIN and ownership record and produces BuildConfiguration and entitlement scope. The transition is deterministic and does not require autonomous model approval.
Why it matters: BuildConfiguration and entitlement scope gives Retrieval agent the evidence needed to begin Retrieve trim-valid manual and campaign content, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/resolve-vin-configuration-and-entitlements
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Retrieval agent performs retrieve trim-valid manual and campaign content using Question plus option codes and model year and produces Applicable manual sections and open campaigns. The transition is deterministic and does not require autonomous model approval.
Why it matters: Applicable manual sections and open campaigns gives Vehicle companion the evidence needed to begin Interpret telemetry and explain the condition, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/retrieve-trim-valid-manual-and-campaign-content
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Vehicle companion performs interpret telemetry and explain the condition using Latest telemetry and diagnostic codes and produces Plain-language explanation with urgency and cited manual text. The transition is deterministic and does not require autonomous model approval.
Why it matters: Plain-language explanation with urgency and cited manual text gives Owner with dealer confirmation the evidence needed to begin Confirm service booking or remote command, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/interpret-telemetry-and-explain-the-condition
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Owner with dealer confirmation performs confirm service booking or remote command using Proposed appointment or remote action and produces Confirmed booking or executed command with audit record. A named human approver must review the evidence before the transition completes.
Why it matters: Confirmed booking or executed command with audit record gives Owner with dealer confirmation the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/confirm-service-booking-or-remote-command
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved VehicleOwnership evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
vehicleOwnerships/tenantId + /vehicleVinAn owner photographs an amber tyre-pressure light; the companion reads the latest telemetry showing the rear-left tyre at 1.9 bar, cites the trim-specific inflation table from the manual, notes an open suspension recall with parts available, and books the dealer visit only after the owner confirms the proposed Thursday slot.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
vehicleOwnerships |
Primary | /tenantId + /vehicleVin |
VehicleOwnership, BuildConfiguration, TelemetrySnapshot, ServiceHistoryEntry, CampaignNotice |
vehicleManualLibrary |
Reference | /tenantId + /manualId |
OwnerManualSection |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
VehicleOwnership |
vehicleOwnerships |
/tenantId + /vehicleVin |
ownership::{vehicleVin} |
None |
BuildConfiguration |
vehicleOwnerships |
/tenantId + /vehicleVin |
build::{vehicleVin} |
None |
OwnerManualSection |
vehicleManualLibrary |
/tenantId + /manualId |
manual::{manualId}::{sectionCode}::{chunkIndex} |
bodyVector |
TelemetrySnapshot |
vehicleOwnerships |
/tenantId + /vehicleVin |
telemetry::{vehicleVin}::{capturedUtc} |
None |
ServiceHistoryEntry |
vehicleOwnerships |
/tenantId + /vehicleVin |
service::{vehicleVin}::{repairOrderId} |
None |
CampaignNotice |
vehicleOwnerships |
/tenantId + /vehicleVin |
campaign::{campaignId}::{vehicleVin} |
None |
Read configuration, latest telemetry, and service history for the VIN in one partition query.
vehicleOwnerships
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.vehicleVin = @vehicleVin AND c.type IN ('VehicleOwnership','BuildConfiguration','TelemetrySnapshot','ServiceHistoryEntry') ORDER BY c.capturedUtc DESC
Knowledge-container query against vehicleManualLibrary (partition-aligned to /tenantId + /manualId): return only manual chunks valid for this VIN's option codes and model year, using the manualId resolved from the build configuration so the read is a single partition query.
vehicleManualLibrary
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.manualId = @resolvedManualId AND c.type = 'OwnerManualSection' AND ARRAY_CONTAINS(c.applicableOptionCodes, @vehicleOptionCode) AND c.modelYearRange.startYear <= @modelYear ORDER BY c.sectionCode ASC
Surface unresolved recalls for the VIN with remedy availability.
vehicleOwnerships
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.vehicleVin = @vehicleVin AND c.type = 'CampaignNotice' AND c.remedyAvailable = true ORDER BY c.safetyPriority DESC
Compare current odometer with the next service interval to propose a booking window.
vehicleOwnerships
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.vehicleVin = @vehicleVin AND c.type IN ('ServiceHistoryEntry','TelemetrySnapshot') ORDER BY c.completedUtc DESC