Automotive & Mobility

Vehicle Owner Companion

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

Confirm service booking or remote command: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

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.

Business problem

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..

Decision to make

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.

Outcome to show

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.

  1. 1Ask a vehicle question in the app
  2. 2Resolve VIN configuration and entitlements
  3. 3Retrieve trim-valid manual and campaign content
  4. 4Interpret telemetry and explain the condition
  5. 5Confirm service booking or remote command

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Owner with dealer confirmation verifies material claims and approves the consequential action.

Workflow stages

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.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved VehicleOwnership evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
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.
Primary aggregate
VehicleOwnership
Primary container
vehicleOwnerships
Hierarchical key
/tenantId + /vehicleVin
Schema version
1

Sample scenario

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.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
vehicleOwnerships Primary /tenantId + /vehicleVin VehicleOwnership, BuildConfiguration, TelemetrySnapshot, ServiceHistoryEntry, CampaignNotice
vehicleManualLibrary Reference /tenantId + /manualId OwnerManualSection

Document types

Contract document types, their owning container, and their identifier pattern.
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

Query patterns