Demo lane · Policy & compliance
Audit-ready answers over security policies.
A config-driven assistant for regulated content: drop policy PDFs in a folder, ingest, and ask access-control, retention, and escalation questions. Every answer carries citations an auditor can trace back to the source document.
Use case
Security and compliance teams with hundreds of policy PDFs who field "where does it say that?" questions and need answers that map to a specific document and chunk, not a vague summary.
Knowledge source
PDF policies in examples/policy_compliance_assistant/policies/ — or any folder set in config.ts. Swapping to a new policy set is a config change, not a code change.
Curated question set
Questions this lane ships with
Defined in config.ts — they run when policy:ask is called with no arguments. Any one-off question can be passed on the command line.
- Summarize the key data retention requirements we must enforce.
- What access controls must auditors review quarterly?
- List the escalation steps if a privacy breach is detected.
Sample run
Captured transcript
No captured run is published for this lane yet. This slot only ever shows verbatim output from a real run — nothing on this page is synthetic. Use the commands in the “Run it locally” section below with credentials and a corpus in place.
Privacy & logging
What gets recorded
- Questions are processed in memory; telemetry records the HMAC-SHA256 hash and length of a query, never its raw text.
- Citations use the policy:// scheme, so answers trace to a document and chunk — not to a user or session.
- Prompt-guard hooks flag attempts to extract system prompts; Sentry events pass through recursive PII scrubbing.
Run it locally
Run it locally
# drop PDFs into examples/policy_compliance_assistant/policies/ npm run policy:ingest npm run policy:ask npm run policy:ask -- "Which roles can approve production access?"
Source: examples/policy_compliance_assistant/config.ts · examples/policy_compliance_assistant/ingest.ts · examples/policy_compliance_assistant/ask.ts