memory-compact

Workspace memory compaction shrinks old daily memory files into thin records while preserving wiki-linked decisions and explicitly retained notes. It drops ephemeral sections like What Happened and Carry Forward to reduce clutter and keep memory searchable.

Before rewriting memory files, the compaction process backs up the original file into cold storage. This makes the memory maintenance operation idempotent and reversible, ensuring safe recoverability for your workspace.

You should run memory compaction when daily memory files exceed your active retention window, such as after a week of daily logs. This scheduled cleanup applies section filtering to reduce clutter and maintain searchable workspace memory.

Yes, memory compaction applies to backfill compaction and safe handling of legacy files that still need retro-promotion. It requires idempotent rewriting to ensure legacy files are processed safely without losing important retained notes.

The best way to retain important notes during memory file compaction is to explicitly mark keep items and wiki-linked decisions. The process preserves these durable entries while dropping ephemeral sections like What Happened and Carry Forward.

A limitation of compacting memory files is that ephemeral sections are dropped during rewriting into thin records. However, cold storage backups of the original file ensure the process remains idempotent and reversible for safe recoverability.