documentation-librarian

Preventing documentation drift requires treating repository docs as a connected, versioned knowledge graph rather than isolated files. This approach detects inconsistencies across README, SPEC, Reference, and ADRs, ensuring cross-document invariants remain stable during changes.

Graph-based documentation governance maintains a coherent knowledge graph to detect drift and align boundaries across README, SPEC, Reference, ADRs, and roadmaps. It preserves correctness and continuity by applying minimal subtree edits instead of rewriting unrelated content.

To repair inconsistent documentation subtrees without rewriting everything, run an incremental subtree repair workflow. This updates only the necessary affected documents to preserve global consistency, generating a concise change report with explicit risk and assumption tags.

You need to bootstrap a documentation knowledge graph when stabilizing cross-document invariants for the first time or aligning boundaries between README, SPEC, and Reference files. This establishes a coherent baseline to detect drift and verify document graph integrity.

Yes, you can use a knowledge graph approach for controlled documentation refactors. It supports controlled refactor workflows that verify document graph integrity, flag risks explicitly, and apply minimal edits to maintain consistency across ADRs and roadmaps.

Documentation graph governance handles assumptions and risks by outputting minimal edits with explicit tags like [ASSUMPTION], [RISK], [PENDING], and [SOURCE]. This traceability ensures flagged risks and assumptions are visible in the concise change report after subtree repairs.