Question
Hypothesis
Can a normal dealership website combine its own structured inventory and lead workflow with deployment-local AI, without routing browser traffic or customer authority through the central Platform?
What this demonstrates
- A Platform template and reviewed Data and Action packages compose the deployment while the customer application remains independently owned.
- The native customer surface consumes a dealership-owned structured inventory API and does not embed backend or runtime service credentials.
- The Companion dock and Max Mode use the public anonymous runtime contract against an assigned, deployment-local LoomAI runtime.
- Strict live checks prove exact inventory actions, grounded comparison, action-plus-RAG fallback for an exact no-match, and honest knowledge boundaries.
- Backend tests verify deployment-scoped authorization plus encrypted, idempotent confirmed lead persistence; the live quality run confirms no write occurs without confirmation.
What this does not demonstrate
- Auto Trader connectivity, endorsement or production data access
- Production dealership adoption or commercial outcomes
Architecture and data flow
- 01 Synthetic source data
- 02 Host application policy
- 03 AI Fabric capability
- 04 Observable UI result
Guided steps
- 01
Browse and filter the clearly labelled fictional dealership inventory.
- 02
Select two vehicles and compare their application-owned facts.
- 03
Open the Companion dock to inspect the assigned-runtime readiness state and expanded Max Mode surface.
Observable evidence
This preview publishes the visible application boundary and names the remaining hosted-runtime gate explicitly. It does not claim public source or completed production evidence.
Security and data boundary
The dealership backend owns stock, exact filters, authorization and lead persistence. Its assigned LoomAI deployment owns retrieval, conversation and action orchestration. The browser receives only public inventory data and runtime-issued anonymous chat access.
All dealership, vehicle and customer records in this preview are fictional. No Auto Trader data is used.
Known limitations
- The preview source adapter uses fictional inventory until approved partner credentials and data rights exist.
- The live demo is evidence of bounded product behavior, not a latency, throughput, conversion or model-quality benchmark.