gap-surfacer

You can track open regulatory compliance gaps by ingesting gap findings into a persistent tracker that de-dupes identical requirement-policy entries, assigns owners, manages lifecycle states, and routes notifications. This maintains a living record of remediation statuses and due dates.

Overdue classification for regulatory gaps respects citation and verification uncertainty by preserving upstream source tags and applying distinct rules that separate true compliance deadlines from pre-rule watch or comment-decision artifacts, ensuring unverified citations are flagged appropriately.

Yes, you can send Slack DM assignment and reminder messages to gap owners. The system enforces per-send user confirmation before delivering notifications, adding extra warnings when citations or compliance conclusions are involved to prevent premature certification.

The best way to generate a status report for regulatory compliance gaps is using dashboard-style outputs that distinguish overdue, due-soon, in-progress, and watch items. These role-specific reports respect CLAUDE.md role configuration and gate compliance certification actions.

You manage the lifecycle state of a regulatory compliance gap by updating its status to open, in-progress, closed, or risk-accepted. The system supports commands for closing or risk-accepting specific gaps while capturing remediation resolution details.

Policy-diff output is the primary ingestion source for identifying gap candidates, but the tracker supports multi-mode operation. You can also produce status report dashboards and manage existing gap lifecycles without requiring new policy-diff ingestion.