gap-surfacer

A regulatory gap tracker organizes compliance policy and procedure gaps by maintaining YAML tracker files. These files record requirements, affected policies, owners, deadlines, and notification status to enforce user-approved communication workflows.

Structured status reporting lists open, due soon, verified overdue, watch, and comment-decision items from your regulatory tracker. This role-based report provides visibility into ongoing policy gaps without triggering unauthorized notifications.

You enforce approval controls by following a guardrailed workflow: show a preview, get explicit yes, and send only with controlled conditions. This prevents unauthorized or unverified notifications in your regulatory compliance workflow.

Yes, you can track partial, full, new-policy, watch, and comment-decision gap types. The system maintains an append-only style registry for gaps created from regulatory feed or diff inputs to support ongoing legal operations.

The compliance tracker separates verified vs non-verified overdue handling to ensure only verified overdue items appear in status reports. This distinction enforces non-automatic, user-approved notification rules and prevents inaccurate deadline management alerts.

Yes, you need to maintain YAML tracker files to use this regulatory gap tracking workflow. These files store the registry of compliance requirements, affected policies, owners, and deadlines required for structured status reporting.