docs-stage-conformance

Documentation drift is detected by auditing docs against stage templates and governance rules to identify missing Related Documents links, duplicate H1s, and target-relative link issues. Conformance checks compare existing docs to templates for structural alignment.

Template conformance for markdown documentation ensures files align with predefined stage templates and governance rules. It involves auditing README indexes and template directories to enforce structural consistency, proper heading hierarchy, and required link presence.

Duplicate H1 headings are fixed by performing a targeted conformance pass on the affected documentation. The process identifies redundant top-level headings and repairs them to ensure only one H1 exists per file, aligning with template governance rules.

Validation evidence is collected and preserved during targeted conformance passes by logging identified template drift, applied repairs, and structural fixes. This evidence supports documentation governance and tracks progress in repository artifacts.

Yes, template conformance checks run without external dependencies. The validation logic operates directly on repository documentation assets, templates, and indexes to detect drift and enforce governance rules natively.

README indexes miss Related Documents links when documentation drifts from stage templates. Running a conformance audit identifies missing links and applies targeted repairs to restore proper template alignment and navigation structure.