Appearance
Regulatory Library Demo Script
Six demos. About fourteen minutes. Turn regulatory complexity into something prospects can see, filter, adopt, and report on—without leaving GhostAI.
This script walks through the Regulatory Intelligence Library: a curated catalog of 80+ frameworks with structured metadata, relationship mapping, one-click alignment with PII detection settings, org-level compliance posture, PDF export for stakeholders, and change alerts for frameworks the customer has adopted. Public catalog data is reference-only; adoption, posture, bookmarks, annotations, exports, and change alerts require an authenticated user in an org with the feature enabled.
Pre-Demo Checklist
- [ ] GhostAI backend and frontend are running; you can open the Regulatory Library experience in the product (or the API base URL you are demoing against, typically
http://localhost:8000). - [ ] Feature flag
regulatory_libraryis enabled for the demo tenant (Business or Enterprise tier in production configurations). - [ ] Demo user is signed in with a role that can adopt frameworks (standard member is sufficient) and, for annotations, an admin or owner account is available if you will show org notes live.
- [ ] Organization vertical (
organization_settings.vertical/ user detection settings vertical) is set to something realistic for the story (for examplehealthcareorfinancial) so Compliance Posture can highlightis_relevantframeworks. - [ ] Browser zoom and resolution allow the relationship graph and jurisdiction map to read clearly (1080p minimum; 1440p preferred).
- [ ] PDF export path verified once before the call:
reportlabinstalled on the backend soGET /api/regulatory-library/posture/exportreturns a file (not a 500). If PDF is unavailable in a sandbox, skip the download click and show the audit event only. - [ ] Optional: clear prior adopted frameworks for the demo user if you need a clean “before” state, or keep one adoption in place to populate change alerts faster.
- [ ] Talking points ready for non-legal disclaimer: the library and posture views are operational aids, not legal advice.
Quick API smoke (optional)
bash
curl -s "http://localhost:8000/api/regulatory-library" | python3 -c "import sys,json; d=json.load(sys.stdin); print(len(d), 'frameworks')"The Story
Alex is a compliance lead at a mid-size company that processes health and financial data. Leadership wants to know which regulations matter, how GhostAI maps to obligations, and what is already “on” in the product. Alex also needs evidence for the next risk committee: a posture summary and a paper trail when frameworks are adopted or reports exported.
Demo 1: Browse Frameworks
Duration: 2 minutes
Goal: Show the full catalog at a glance and prove filtering works.
What to show
- Open the framework list (all frameworks).
- Walk one row end-to-end and name the fields the UI surfaces from the summary payload:
id— stable catalog key (used in URLs and adopt calls).abbreviation— short label (HIPAA, GDPR, PCI DSS, …).full_name— official or canonical title.jurisdiction— object withtype(us_federal,us_state,eu,uk,international,industry, …) andregions(for example["CA"],["NY"], or empty when not state-scoped).jurisdiction_flag— compact visual hint for the map (emoji or flag token in the catalog).industries— vertical tags such ashealthcare,financial,technology(used for relevance and applicable scoring).ghostai_readiness_level—full,partial, orawareness(how completely GhostAI can operationalize the framework today).status—active,proposed, orsuperseded.- Plus
description,category, andtagsfor discovery.
Live filter (talk while you click)
- Category — e.g. restrict to
HealthcareorPrivacy(category is case-insensitive in search). - Jurisdiction — filter by
jurisdiction.type(for exampleeuorus_federal). - Optionally region —
jurisdiction_regionmatches a code injurisdiction.regions(e.g.CAfor CCPA-style state frameworks).
Talking points
“This is not a static PDF. Every row is structured data we ship with the product—abbreviation, full name, jurisdiction model, industries, readiness level, and lifecycle status—so you can filter the same way an API client would.”
“Search hits abbreviation, full name, description, citation, GhostAI support text, tags, and requirement titles—so ‘tokenization’ or ‘BAA’ actually finds frameworks, not just acronyms.”
Behind the scenes: GET /api/regulatory-library returns summaries; GET /api/regulatory-library/search accepts q, category, jurisdiction, jurisdiction_region, industry, data_type, and readiness.
Demo 2: Framework Detail
Duration: 2 minutes
Goal: Prove depth: enforcement, penalties, obligations mapped to product, and lineage.
Pick one strong example
Use a framework your audience cares about (e.g. HIPAA hipaa or GDPR gdpr). Scroll the detail view and narrate:
| Area | Field(s) | What to say |
|---|---|---|
| Identity | id, abbreviation, full_name, description, category, jurisdiction, jurisdiction_flag, industries, ghostai_readiness_level, tags, status | Same core identity as the list, plus narrative context. |
| Enforcement | enforcement_body, penalty_summary, max_penalty | max_penalty is structured: amount, unit (per_violation, per_year, percent_revenue, per_record, …), and human basis. |
| Obligations | key_requirements[] | Each item has title, description, and ghostai_feature — the bridge from legal language to a togglable capability (e.g. PII detection, tokenization, audit logging). |
| Data | protected_data_types | Taxonomy IDs such as phi, pii, npi — ties into filters and applicable scoring. |
| Scope | applicable_to | Who typically falls in scope (plain-language roles or entity types). |
| Graph | related_frameworks[] | id plus relationship: complements, extends, supersedes, overlaps, implements. |
| Authority | citation, effective_date, last_amended, external_url | Traceability for audits and policy work. |
| Product | ghostai_support, ghostai_features, upcoming_changes | How GhostAI talks about coverage; what is on the roadmap or changing in the regime. |
| Versioning | version, last_verified | Catalog freshness signals. |
Talking points
“Requirements are not blobs of text—we tie each obligation to a GhostAI feature so your security and GRC teams can argue in the same vocabulary as the product toggles.”
“Related frameworks are typed edges, not guesswork: complements versus extends versus supersedes.”
Behind the scenes: GET /api/regulatory-library/{framework_id} returns the full detail projection.
Demo 3: Relationship Graph and Jurisdiction Map
Duration: 3 minutes
Goal: Visual literacy—how frameworks connect and where they apply.
Relationship graph
- Open the graph view fed by
GET /api/regulatory-library/graph. - Explain
nodes:id,abbreviation,category,full_name,ghostai_readiness_level,connection_count. - Explain
edges:source,target,relationship(same vocabulary asrelated_frameworks). - Interact: pan/zoom, hover a high-
connection_counthub (often AI governance or core privacy frameworks), follow one edge aloud (“GDPR complements UK GDPR”).
Jurisdiction map
- Open the map (or regional visualization) that uses
jurisdiction.typeandjurisdiction.regions. - Highlight regions: for
us_stateframeworks, emphasize state codes inregions; foreu, show European coverage; forinternational, clarify scheme-based scope rather than a single country. - Tie back to Demo 1: the same
jurisdictionobject drives both the list filters and the map.
Talking points
“Compliance is a graph problem as much as a checklist. We ship the edges explicitly so your team can see clusters—AI governance, US privacy patchwork, financial stack—without manually building link tables.”
“Jurisdiction is first-class: type plus optional regions, so California and New York don’t look like generic ‘US’ rows.”
Behind the scenes: Graph data is GET /api/regulatory-library/graph. List/search already expose jurisdiction for map layers.
Demo 4: Adopt a Framework
Duration: 2 minutes
Goal: One action merges recommended entity types and thresholds into the user’s PII detection settings; show undo.
Steps
- From a framework detail screen, click Adopt (or equivalent).
- Show the confirmation payload or toast: the user’s adopted regulations list now includes this framework
id. - Open PII / detection settings (or the developer view if technical audience) and point out newly enabled entities and any tighter thresholds (adopt only adds entities and lowers thresholds when recommended values are stricter—see implementation).
- Click Unadopt and show entities that become orphaned (only referenced by that framework) removed, and thresholds recomputed from remaining adoptions.
Talking points
“Adopt is not a sticker on a slide—it merges the framework’s recommended detectors and sensitivity into your active configuration.”
“Unadopt is a real rollback: we remove orphaned entities and rebuild thresholds from what you still have adopted.”
Behind the scenes:
POST /api/regulatory-library/{framework_id}/adopt— merges entities + thresholds; idempotentalready_adoptedresponse if repeated.POST /api/regulatory-library/{framework_id}/unadopt— removes regulation, prunes orphaned entities, resets thresholds via merged recommendations.
Audit: COMPLIANCE_FRAMEWORK_ADOPT, COMPLIANCE_FRAMEWORK_UNADOPT (resource type compliance framework, details include entities and threshold deltas).
Demo 5: Compliance Posture
Duration: 3 minutes
Goal: Show org-level readiness mapped from ghostai_features to what is actually configured; export a PDF for the committee.
Posture grid
Open Compliance Posture for the signed-in org.
For each framework row, explain:
framework_id,abbreviation,categoryis_relevant—truewhen the org’s vertical (fromorganization_settings.vertical/ detection settings) appears in the framework’sindustrieslistreadiness—configured,partial, ornot_configuredbased on how manyghostai_featuresthe product treats as satisfied (PII detection, tokenization, compliance tagging when enabled, and a set of platform capabilities such as audit logging, RBAC, encryption, TLS, MFA)configured_featuresvsmissing_featurestotal_features,configured_count
Sort or filter mentally: “start with
is_relevantandpartial—that’s your punch list.”
PDF export
- Click Export PDF (or hit the export endpoint from a scripted environment).
- Show the downloaded
ghostai-compliance-posture.pdf: adopted frameworks, per-framework entity coverage table, and optional “not yet adopted but relevant to your vertical” section. - Mention the disclaimer footer (informational, not legal advice).
Talking points
“Posture is honest: we compare each framework’s ghostai_features to what your tenant actually has on—not a generic marketing checklist.”
“The PDF is board-ready: adopted frameworks, entity coverage, and gaps—plus an audit event when someone generates it.”
Behind the scenes:
GET /api/regulatory-library/posture— JSON posture array.GET /api/regulatory-library/posture/export—application/pdfstream.
Audit: COMPLIANCE_REPORT_EXPORT with details including adopted and entity counts.
Demo 6: Change Alerts and Glossary
Duration: 1 minute
Goal: Close with “we help you stay current” and define terms on demand.
Change alerts
- Ensure at least one adopted framework in the user’s detection settings has non-empty
upcoming_changesin the catalog. - Open Change alerts (or
GET /api/regulatory-library/change-alertsin a technical sidebar). - Show each alert:
framework_id,abbreviation,upcoming_changes,last_amended.
Glossary
- Open the glossary or link from a term in the UI.
- Show a term record:
id,term,definition,frameworks[](related framework ids),related_terms[]. - Optional: deep-link a single term via
GET /api/regulatory-library/glossary/{term_id}(for examplecovered_entity).
Talking points
“Alerts are scoped to what you adopted—we don’t noise the whole library, only the regimes you said matter for your configuration.”
“The glossary links terms back to frameworks so new hires can read a definition and immediately see which obligations use that language.”
Behind the scenes: GET /api/regulatory-library/change-alerts (authenticated); GET /api/regulatory-library/glossary and GET /api/regulatory-library/glossary/{term_id} (public).
Reference: Applicable Scoring API
For bespoke demos (vertical + data types + jurisdictions), you can show GET /api/regulatory-library/applicable with:
industries— comma-separated industry ids (e.g.healthcare,financial)data_types— comma-separated taxonomy ids (e.g.phi,pii)jurisdictions— comma-separated jurisdiction types (e.g.us_federal,eu)
Each match returns a summary plus relevance_score (weighted matches across the three dimensions).
Reference: Bulk Adopt and Collaboration
POST /api/regulatory-library/bulk-adoptwith JSON body{ "framework_ids": ["hipaa", "hitech", ...] }— adopts many at once; auditCOMPLIANCE_BULK_ADOPTwith the set of new adoptions.- Bookmarks (user-level):
GET /api/regulatory-library/bookmarks,POST /api/regulatory-library/bookmarks/{framework_id}(toggle). - Annotations (org-level, admin/owner):
GET/POST /api/regulatory-library/annotations/{framework_id},DELETE /api/regulatory-library/annotations/{annotation_id}.
Reference: Supporting Public Endpoints
| Endpoint | Purpose |
|---|---|
GET /api/regulatory-library/categories | Category histogram |
GET /api/regulatory-library/data-types | Data-type taxonomy with framework counts |
GET /api/regulatory-library/timeline | Frameworks with effective_date, last_amended, upcoming_changes |
GET /api/regulatory-library/penalties | Penalty comparison dataset (penalty_summary, max_penalty) |
Audit Actions (Compliance)
| Action | When |
|---|---|
COMPLIANCE_FRAMEWORK_ADOPT | Single framework adopt |
COMPLIANCE_FRAMEWORK_UNADOPT | Single framework unadopt |
COMPLIANCE_BULK_ADOPT | Bulk adopt completed with at least one new framework |
COMPLIANCE_REPORT_EXPORT | Posture PDF generated |
Time Box (~14 minutes)
| Demo | Minutes |
|---|---|
| 1 Browse | 2 |
| 2 Detail | 2 |
| 3 Graph + map | 3 |
| 4 Adopt / unadopt | 2 |
| 5 Posture + PDF | 3 |
| 6 Alerts + glossary | 1 |
| Total | 13 (buffer to 16 with questions) |
If You Only Have Five Minutes
Do Demo 1 (filter to the prospect’s vertical), Demo 2 (one framework’s key_requirements + ghostai_feature), and Demo 4 (adopt + settings delta). Mention posture PDF and audit as the enterprise finish.