docguard-review

Documentation drift is detected through read-only cross-reference audits that compare terminology and claims across document collections to surface semantic misalignment and gaps. This analysis verifies coherence between implementation and supporting files without modifying any content.

Auditing broken cross-references requires validating cross-document coherence by inspecting links and dependencies across canonical docs, support files, and specs. The process generates a severity-ranked report detailing integrity issues and coverage gaps without altering the original files.

Terminology consistency is checked by performing cross-document comparisons that identify contradictions and semantic gaps across all documentation sets. This read-only quality assessment evaluates completeness and clarity, returning severity-ranked recommendations to ensure one coherent story.

Documentation review does not modify original files because the quality assessment relies entirely on read-only inspection. It analyzes coverage gaps, broken references, and terminology inconsistencies, returning a structured report of findings ranked by severity without touching the source documents.

A cross-reference audit is needed when preparing a release or after recent implementation changes to verify that architecture notes, specs, and support files still align. This read-only analysis surfaces drift, broken references, and coverage gaps before they confuse readers.

Assessing documentation drift without modifying files limits the process to read-only inspection and reporting, meaning it cannot automatically fix broken cross-references or rewrite inconsistent terminology. It outputs severity-ranked findings and validation results for manual correction instead.