memory-consolidate

You can check memory coherence by running a read-only audit that detects semantic inconsistencies, duplicates, and open blocks across MEMORY.md, LESSONS.md, and DECISIONS.md. It provides an actionable summary without modifying any files.

Semantic drift detection identifies inconsistencies across MEMORY.md, LESSONS.md, and DECISIONS.md. It checks for misaligned dates, duplicates, open blocks, and broken cross-file references to ensure project documentation remains accurate.

Yes, you can validate project memory before a release without altering files by using a read-only quality assurance check. It reports findings and guidance on restoring coherence while ensuring no modifications are made to the documentation.

To find duplicate entries and broken cross-file references in markdown documentation, apply read-only drift-detection checks. This generates an actionable summary highlighting inconsistencies to help restore memory coherence across the project.

The best way to prevent documentation drift in project memory files is to perform regular read-only coherence audits. This identifies semantic inconsistencies, validates dates, and checks cross-file references to maintain alignment across MEMORY.md, LESSONS.md, and DECISIONS.md.