memory-health

To validate memory data integrity, run automated tests that cross-check file counts, indexes, and references across interconnected markdown files. This process identifies desyncs and generates a health report detailing exactly what is broken and how to fix it.

Inconsistent problem counts and missing references occur because interconnected markdown files drift over time after bulk edits or deletions. Running an integrity health check validates file counts, indexes, and details across all memory artifacts to surface these mismatches.

The best way to fix data desync is to execute an integrity check tool that validates file counts, indexes, and details across all memory artifacts. It enforces automated tests and manual checks to produce a final health report with suggested fixes.

You should run a memory health check when you suspect data desync, after performing bulk edits, or for periodic maintenance. This ensures that dossier references, observation indexes, and problem counts stay synchronized across your markdown files.

A memory integrity test validates cross-references between markdown files, ensuring dossier references, observation indexes, and problem counts match their detail sections. It also assesses freshness, file size, and duplicates to surface actionable cleanups.