The composite case study
How the wedge actually lands, told once, properly. This is an anonymized composite — “a healthcare voice-AI vendor pursuing ISO 42001” — drawn from real deal experience with identifying details deliberately removed. Treat it as a story shape, not a citable account: no names, no figures, no deployment specifics belong in any retelling. GROUNDED · KB
The arc, in five beats
Section titled “The arc, in five beats”1. The trigger event. A healthcare voice-AI vendor — ambient clinical documentation, so PHI flows through every inference — comes out of a security audit and pivots to pursuing ISO/IEC 42001 certification, because its own enterprise buyers are starting to ask for proof of AI governance. The door opens on a compliance motion, not an insurance one.
2. The demo that changed the room. Glacis showed auto-generated ISO 42001 control coverage: the standard’s controls mapped against live evidence sources, produced by an engine rather than a consultant’s spreadsheet. The assessment showed a majority of controls already evidenced or partially evidenced by runtime attestation — with the remainder identified honestly. The effect was categorical: a technical evaluation became a procurement conversation in a single meeting, because the vendor could suddenly see certification as an artifact of infrastructure it would run anyway.
3. The land. A deliberately scoped runtime deployment: a governed passthrough in front of the vendor’s existing model provider, deterministic controls on input and output, a declared baseline with drift detection, and notarized receipts — the Scan / Enforce / Notarize loop in miniature. Scoped means scoped: governed paths only, stated plainly.
4. The trust posture that closed it. Two commitments did the closing work:
- Zero egress. Raw prompts and responses — the PHI — never leave the customer’s environment; only hashes and signed metadata cross the trust boundary. For a healthcare vendor, this converts “another vendor sees our data” from a dealbreaker into a non-event. GROUNDED · Labs
- Honesty about assurance level. Glacis stated what its deployment mode could and could not claim — naming the assurance level it doesn’t reach rather than waiting to be asked. See the AAL honesty rule in 19-02.
5. The lesson: honesty is the pitch. The vendor had been pitched by plenty of vendors claiming everything. The one that said “here is our boundary, and here is the proof inside it” was the one that got the deal. The canonical scope claim — receipts “are silent about un-mediated paths” — read as engineering seriousness, not weakness.
What to reuse, and what never to reuse
Section titled “What to reuse, and what never to reuse”| Reusable (the shape) | Never reusable (the specifics) |
|---|---|
| Security-audit or certification pursuit as the trigger event | Any customer or person name |
| Auto-generated control coverage as the eval→procurement converter | Coverage percentages or gap counts — say “a majority of controls” and stop |
| Scoped runtime deployment as the land | Deployment regions, URLs, architecture internals |
| Zero-egress + stated assurance boundary as the close | Anything from inside an NDA |
The discipline mirrors the claim taxonomy: the story’s mechanics are assertable because they describe how the product works; the story’s particulars are someone else’s confidences.
Drill this page →13 bank questions stand behind what you just read. Check it while it’s warm.