self_reflection

Memory auditing works by scanning memory vaults and relationship links to detect duplicates, gaps, stale entries, and broken references. It flags conflicts and prompts for user confirmation before applying any corrections to maintain knowledge base trust.

You resolve memory conflicts by triggering a consistency audit that surfaces contradictions and broken links. The system proposes specific corrections, requiring your consent before it applies updates and rebuilds the vault to restore data quality.

Yes, memory auditing requires memory query tools to scan vaults and relationships effectively. It also utilizes the Row-Bot workflow to propose, confirm, and apply corrections for detected duplicates and contradictions.

You should run a memory consistency audit when memories become outdated or conflict. Scanning for gaps, stale entries, and broken relationships ensures your knowledge base remains accurate and maintains long-term trust.

The best way to clean up duplicate entries is to perform a memory audit that scans the vault and its relationships. The system flags duplicates and guides corrections through a consent-based workflow to ensure safe updates.