Approved scope
The buyer's named counsel or compliance owner identifies the duty and approves the text.
Fictional product · not a client
A patch you can inspect,
not a promise you must trust.
This fictional support agent demonstrates one narrow engineering pattern: making an AI-interaction disclosure visible at the start of the first interaction, then recording test evidence. The example does not establish that this pattern is legally sufficient for any real product.
Interactive proof
Northstar support assistant
Switch between states. The product, transcript, company, and test record are invented solely to demonstrate implementation quality.
Support assistantOnline
You are interacting with an AI support assistant.
Type a message…
What the real bundle contains
Evidence with its limits attached.
Change record
Repository, surfaces, components, commit identifiers, staging version, and review owner.
Test output
Automated behavior results plus manual keyboard, screen-reader, contrast, and responsive checks.
Known limits
Excluded flows, third-party dependencies, unresolved vendor questions, and production-release ownership.
Hear the qualification boundaries. Play or download the fictional voice demo ↗ and read the exact transcript ↗. This is a local text-to-speech rendering, not a recording of a phone call. It does not prove carrier connectivity, number routing, or production telephony.
Download the fictional evidence record (JSON) → It contains no client data and makes no legal determination. Inspect the source and passing tests on GitHub ↗
Your product will need its own approved scope.