memory-audit

To audit memory organization, run the memory-audit script to categorize MEMORY.md entries and generate rollup proposals. It classifies entries as load-bearing, archival, superseded, or drifted to maintain project memory organization.

Managing outdated MEMORY.md entries involves categorizing them as superseded or drifted. This audit process identifies unnecessary files and suggests rollup moves to consolidate entries for better code organization.

Categorizing project memory files is done by running an audit script that evaluates your auto-memory directory. It automatically classifies MEMORY.md entries into load-bearing, archival, superseded, or drifted categories.

Yes, you can audit a custom memory directory path by executing the script with the `--memory-dir <path>` flag. The script defaults to the standard directory if no custom path is provided.

You should run a memory audit when managing a large project with many MEMORY.md entries. It helps identify entries that are no longer relevant, need to be archived, or require consolidation through rollup proposals.

Memory organization via scripts requires direct script execution to perform file operations. It relies on the script's ability to categorize entries and suggest rollups, meaning manual review of proposed moves is still necessary.