compliance_audit

To audit your repository for Phoenix Protocol v13.0 compliance, run a scan against your target directory. The tool recursively checks Markdown and Python files, validating UIP headers and structural geometry, then generates a PASS/WARNING/FAIL report.

A documentation governance check looks for required UIP keys, verifies evolution alignment, and enforces geometry rules like a single H1 singularity. It flags structural formatting violations and indentation issues to ensure files meet protocol standards.

Yes, you can use structural linting for pre-merge validation of governed artifacts. The tool scans file paths to detect metadata and formatting violations, outputting a numeric quality score and consolidated audit report to block non-compliant merges.

The best way to validate UIP headers across a documentation directory is to run a recursive directory-wide scan. This automatically skips noise folders, detects required UIP keys, and saves a consolidated audit report with per-file quality scores.

Your compliance audit report shows a WARNING for filename patterns because the scanner detected file names that do not match expected naming conventions. This serves as a structural linting alert to help you correct naming before final governance readiness checks.

Yes, repository scanning skips common noise folders during documentation governance checks. This ensures the compliance audit targets actual Markdown and Python artifacts, preventing build directories from skewing the final PASS/WARNING/FAIL results.