rai-docs-update

To keep module documentation frontmatter aligned with code changes, sync governance/architecture/modules/*.md files against a built knowledge graph to detect and repair drift in dependencies, public APIs, and component counts after story closure.

Documentation drift in a project knowledge graph occurs when module Markdown frontmatter fields like depends_on, depended_by, public_api, and components no longer match the actual codebase architecture and recent code diffs.

Detect architecture documentation drift by building the knowledge graph at .raise/rai/memory/index.json, reading recent diffs to identify affected modules, and comparing their frontmatter to graph-derived truths to produce a drift report.

Automated frontmatter updates are restricted to allowed fields only and require a human-in-the-loop approval gate for narrative text changes, ensuring safe drift repair while maintaining documentation coherence.

Updating documentation frontmatter requires a pre-built knowledge graph located at .raise/rai/memory/index.json and module docs stored in governance/architecture/modules/*.md to perform accurate drift comparison and coherence checks.

The best way to close the coherence loop after applying frontmatter updates is to rebuild the knowledge graph from the updated repository state and present a concise summary of the applied changes and detected drift repairs.