h4tcher-governance-check

Pre-audit governance validation requires checking lean file line-count thresholds, scanning markdown for banned anti-slop phrases, and verifying audit-cycle invariants across constitution, domain, and baseline artifacts to catch quality regressions before an audit runs.

Invariant checking validates AUDIT summary-table math, tier weights, domain coverage, and finding registry reference integrity to ensure structured pass/fail health reports accurately reflect governance system state.

Detect governance drift and quality regressions by scanning multiple governance markdown files and JSON registries to compute counts, verify table consistency, and validate baseline schema completeness alongside P1-P8 pillar coverage between audit cycles.

Yes, automated checks verify baseline schema completeness and ensure each pillar (P1-P8) maintains primary governance coverage with traceability for repositories using domain-based audit governance systems.

Audit readiness validation requires reading multiple governance markdown files and JSON registries to compute counts, apply table consistency rules, verify finding registry state, and output a structured pass/fail health report.