rcode-memory-audit

Memory drift occurs when project memory files contain stale entries, contradictions, and out-of-sync distillates that no longer match source material. It causes teams to lose trust in milestone tracking, incident logs, and decision records that guide delivery work.

A memory bank audit report includes severity-tagged findings grouped by file, covering stale entries, contradictions, missing template content, and items requiring archival. Each finding provides a concise one-line fix suggestion without modifying any files.

Run a memory bank freshness check when project files feel inconsistent, a milestone has gone quiet, or before relying on the bank for planning and delivery. It validates that distillates and stack references are still in sync with their source material.

Yes, auditing decision records and incident logs returns findings without modifying any files. The audit outputs a severity report with one-line fix suggestions, leaving all archival and correction actions to the team for manual review.

The best way to find missing template content is to run a template and freshness review across the memory bank. It detects unfilled placeholders, empty archive-like folders, and distillates that have fallen out of sync with their source material.