Documentation Alignment

To audit Markdown files for missing documentation headers, run a compliance scanner against your repository to detect absent mandatory Block A and Block G boundary markers and report per-file status. This identifies exactly which artifacts deviate from required structural templates.

Template enforcement for documentation governance ensures Markdown and Python artifacts strictly conform to standardized header boundaries. It uses deterministic regex and template validation to check for mandatory structural blocks, preventing documentation drift across repository-wide ingestion.

You can normalize legacy Markdown documentation by performing high-density structural alignment across a directory. This process automatically injects standardized UIP-V15 header blocks and anchors into non-compliant files, bringing many legacy artifacts back into resonance with registry standards.

Yes, you can enforce Python file header compliance alongside Markdown in the same audit. The compliance auditor checks both .py and .md targets for mandatory boundary markers and structural alignment, injecting standardized header content into non-compliant Python artifacts.

The best way to automatically inject standardized headers is to run the structural harmonization process across your target directory. It automatically inserts the required UIP-V15 header blocks plus an Omni-Anchor into non-compliant files while emitting SELT shadow logs for every run.

No external dependencies are required to perform structural alignment checks on your documentation. The Skill operates independently using deterministic regex and template validation to audit and inject mandatory structural blocks across your Markdown and Python files.