Source & permission
PUBLIC DEMONSTRATION
Local synthetic records in the public demonstration.
BEFORE A LIVE PILOT
Authorised sources, purpose, licensing and permitted uses documented.
TRUST & READINESS / CURRENT POSITIONClear sources.
Clear sources.
Explicit boundaries.
Inspectable work.
Understand what the public prototype does today and the decisions and controls that must be verified before a live customer workflow.
Inspect the readiness registerSynthetic inputs.
Local example.
No live care connector.
EvidenceOriginal question retained
ResponsibilitySimulated care role
ControlsLive implementation to validate
IMPLEMENTED IN THE EXAMPLE / REQUIRED BEFORE LIVE USEKnow what is demonstrated.
Know what is demonstrated.
Know what remains.
Experience and Care are demonstrated here through a browser example, rather than a released self-service application. A live engagement requires implemented controls and agreed acceptance checks.
Identity & access
PUBLIC DEMONSTRATION
No real customer or employee accounts in the demo.
BEFORE A LIVE PILOT
Authentication, role enforcement and customer separation implemented and tested.
Hosting & retention
PUBLIC DEMONSTRATION
The interactive care example runs in browser memory.
BEFORE A LIVE PILOT
Hosting region, encryption, retention, backups and deletion responsibilities agreed and verified.
Delivery & recovery
PUBLIC DEMONSTRATION
Simulated receipt, failed handoff, retry and duplicate prevention.
BEFORE A LIVE PILOT
Real acknowledgements, durable delivery, safe retries, monitoring and incident ownership validated.
AI & human review
PUBLIC DEMONSTRATION
Fixed example responses. No AI service processes these records.
BEFORE A LIVE PILOT
Any assistance evaluated on permitted evidence, visible uncertainty and human approval.
Export & exit
PUBLIC DEMONSTRATION
A synthetic example record can be exported as JSON.
BEFORE A LIVE PILOT
Live data ownership, export format, access removal and exit process agreed and tested.
PERMITTED SOURCES / VISIBLE UNCERTAINTYA connection has a basis.
A connection has a basis.
A conclusion needs evidence.
The product direction is source-aware. Collection, matching and interpretation each need a clear purpose and an accountable review.
Product identity
The example knows the fictional product from its entry. A shared QR destination does not identify a person or establish an individual pack’s batch.
External listening
Reviews and social sources are roadmap work. Supported access, licensing, freshness and coverage need source-by-source validation.
Customer evidence
A customer-supplied reference stays labelled as supplied. Repeated reports do not by themselves prove a common cause or a product safety conclusion.
Assistance & decisions
The current response text is fixed example content. Any future AI assistance needs original evidence, evaluated behaviour and human review.
USING THIS WEBSITEThe example and the enquiry
The example and the enquiry
are separate journeys.
The care demonstration runs in browser memory. Reloading clears the example case; an export contains synthetic data. The separate enquiry form asks for contact details so the team can reply. Read the privacy information before submitting an enquiry.
Bring the questions
your review team will ask.
Hosting, access, retention, source rights, recovery and exit belong in the pilot brief.
Explore the pilot plan