Skip to content

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_library is 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 example healthcare or financial) so Compliance Posture can highlight is_relevant frameworks.
  • [ ] 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: reportlab installed on the backend so GET /api/regulatory-library/posture/export returns 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 ​

  1. Open the framework list (all frameworks).
  2. 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 with type (us_federal, us_state, eu, uk, international, industry, …) and regions (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 as healthcare, financial, technology (used for relevance and applicable scoring).
    • ghostai_readiness_level — full, partial, or awareness (how completely GhostAI can operationalize the framework today).
    • status — active, proposed, or superseded.
    • Plus description, category, and tags for discovery.

Live filter (talk while you click) ​

  • Category — e.g. restrict to Healthcare or Privacy (category is case-insensitive in search).
  • Jurisdiction — filter by jurisdiction.type (for example eu or us_federal).
  • Optionally region — jurisdiction_region matches a code in jurisdiction.regions (e.g. CA for 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:

AreaField(s)What to say
Identityid, abbreviation, full_name, description, category, jurisdiction, jurisdiction_flag, industries, ghostai_readiness_level, tags, statusSame core identity as the list, plus narrative context.
Enforcementenforcement_body, penalty_summary, max_penaltymax_penalty is structured: amount, unit (per_violation, per_year, percent_revenue, per_record, …), and human basis.
Obligationskey_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).
Dataprotected_data_typesTaxonomy IDs such as phi, pii, npi — ties into filters and applicable scoring.
Scopeapplicable_toWho typically falls in scope (plain-language roles or entity types).
Graphrelated_frameworks[]id plus relationship: complements, extends, supersedes, overlaps, implements.
Authoritycitation, effective_date, last_amended, external_urlTraceability for audits and policy work.
Productghostai_support, ghostai_features, upcoming_changesHow GhostAI talks about coverage; what is on the roadmap or changing in the regime.
Versioningversion, last_verifiedCatalog 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 ​

  1. Open the graph view fed by GET /api/regulatory-library/graph.
  2. Explain nodes: id, abbreviation, category, full_name, ghostai_readiness_level, connection_count.
  3. Explain edges: source, target, relationship (same vocabulary as related_frameworks).
  4. Interact: pan/zoom, hover a high-connection_count hub (often AI governance or core privacy frameworks), follow one edge aloud (“GDPR complements UK GDPR”).

Jurisdiction map ​

  1. Open the map (or regional visualization) that uses jurisdiction.type and jurisdiction.regions.
  2. Highlight regions: for us_state frameworks, emphasize state codes in regions; for eu, show European coverage; for international, clarify scheme-based scope rather than a single country.
  3. Tie back to Demo 1: the same jurisdiction object 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 ​

  1. From a framework detail screen, click Adopt (or equivalent).
  2. Show the confirmation payload or toast: the user’s adopted regulations list now includes this framework id.
  3. 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).
  4. 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; idempotent already_adopted response 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 ​

  1. Open Compliance Posture for the signed-in org.

  2. For each framework row, explain:

    • framework_id, abbreviation, category
    • is_relevant — true when the org’s vertical (from organization_settings.vertical / detection settings) appears in the framework’s industries list
    • readiness — configured, partial, or not_configured based on how many ghostai_features the 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_features vs missing_features
    • total_features, configured_count
  3. Sort or filter mentally: “start with is_relevant and partial—that’s your punch list.”

PDF export ​

  1. Click Export PDF (or hit the export endpoint from a scripted environment).
  2. 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.
  3. 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/pdf stream.

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 ​

  1. Ensure at least one adopted framework in the user’s detection settings has non-empty upcoming_changes in the catalog.
  2. Open Change alerts (or GET /api/regulatory-library/change-alerts in a technical sidebar).
  3. Show each alert: framework_id, abbreviation, upcoming_changes, last_amended.

Glossary ​

  1. Open the glossary or link from a term in the UI.
  2. Show a term record: id, term, definition, frameworks[] (related framework ids), related_terms[].
  3. Optional: deep-link a single term via GET /api/regulatory-library/glossary/{term_id} (for example covered_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-adopt with JSON body { "framework_ids": ["hipaa", "hitech", ...] } — adopts many at once; audit COMPLIANCE_BULK_ADOPT with 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 ​

EndpointPurpose
GET /api/regulatory-library/categoriesCategory histogram
GET /api/regulatory-library/data-typesData-type taxonomy with framework counts
GET /api/regulatory-library/timelineFrameworks with effective_date, last_amended, upcoming_changes
GET /api/regulatory-library/penaltiesPenalty comparison dataset (penalty_summary, max_penalty)

Audit Actions (Compliance) ​

ActionWhen
COMPLIANCE_FRAMEWORK_ADOPTSingle framework adopt
COMPLIANCE_FRAMEWORK_UNADOPTSingle framework unadopt
COMPLIANCE_BULK_ADOPTBulk adopt completed with at least one new framework
COMPLIANCE_REPORT_EXPORTPosture PDF generated

Time Box (~14 minutes) ​

DemoMinutes
1 Browse2
2 Detail2
3 Graph + map3
4 Adopt / unadopt2
5 Posture + PDF3
6 Alerts + glossary1
Total13 (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.

SOC 2 Type II Certified | BAA Available | HIPAA-Ready