PII Redaction
Strips personal identifiers (SSNs, account numbers) before the model ever sees them.
Module 01 · Govern · Interactive lesson
A real request doesn't go straight to the model. It runs a gauntlet: input guardrails scrub and gate it, the model drafts an answer, and output guardrails decide whether that answer can ship. Pick a request below and watch each checkpoint do its job.
Choose a request
Local rules: an SSN like 123-45-6789 triggers redaction; words like sue or prescription trip the scope gate; am I eligible forces a citation/review hold.
The pipeline
Input → Model → Output
Strips personal identifiers (SSNs, account numbers) before the model ever sees them.
Confirms the request is in-mission. Off-limits topics (legal, medical advice) are refused here.
Drafts a benefits answer from the sanitized, in-scope request.
Every eligibility claim must trace to a cited source. Uncited claims are held, not shipped.
Nothing auto-submits. High-stakes answers route to a human before any veteran sees them.
Request text as it flows
How do I check the status of my VA disability claim?
Awaiting a request.
Input guardrail
Strips personal identifiers (SSNs, account numbers) before the model ever sees them.
Input guardrail
Confirms the request is in-mission. Off-limits topics (legal, medical advice) are refused here.
Model
Drafts a benefits answer from the sanitized, in-scope request.
Output guardrail
Every eligibility claim must trace to a cited source. Uncited claims are held, not shipped.
Output guardrail
Nothing auto-submits. High-stakes answers route to a human before any veteran sees them.
Why this matters
This is GOVERN in motion. Every claim that reaches a veteran is citation-backed, every high-stakes answer passes a human-in-the-loop, and nothing auto-submits. The model is powerful, but it never gets the last word — the guardrails do.
Mission first, people always.