governance-audit-practicelisted

# Governance Audit Practice The methodology for conducting governance audits. This skill guides the governance-auditor agent through semantic drift detection, debt inventory, and frame alignment review. It is also used by the `/governance-audit` command. A governance audit answers one question: **does the meaning encoded in your governance constraints still correspond to the reality they are meant to govern?** ## When to Audit - **Quarterly**: as part of the operating cadence (alongside `/assess` and `/harness-audit`) - **After significant change**: when the technology, process, or regulatory environment that governance constraints reference has changed substantially - **On suspicion**: when a team member notices that governance language no longer matches what the team actually does ## Audit Process ### 1. Identify Governance Constraints Scan HARNESS.md for constraints that encode governance requirements. A constraint is governance-related if it: - References a regulation, policy, standard, or compliance requirement - Uses governance language (fairness, transparency, oversight, accountability, compliance, safety, responsible, ethical) - Has a `Governance requirement` field in the extended template ### 2. Score Falsifiability For each governance constraint, assess falsifiability on a three-point scale: | Score | Meaning | Signal | | --- | --- | --- | | Falsifiable | Has specific verification criteria, defined evidence, clear failure action | Healthy | | Pa