recover-from-staleness-drift

To reconcile memory bank documentation with a codebase, run a staleness audit to detect drift, capture the current architecture, update entries with evolution notes, and validate file paths to restore alignment.

Documentation staleness and drift occur when memory bank entries fail to track codebase evolution, causing misaligned file paths and outdated architectural patterns that require systematic reality auditing to correct.

Audit stale documentation by comparing memory bank entries against the actual repository structure, capturing active patterns, updating locations with evolution notes, and enforcing rigorous validation checks.

Yes, you can prevent future memory bank drift by implementing preventive measures that sustain documentation accuracy over time, enforcing traceable changes and practical checks for new engineers.

Yes, the staleness audit works without external dependencies, systematically guiding the reconciliation of memory bank documentation with the current codebase to restore alignment and preserve historical context.