memory-promote

To promote staged memory updates, the process verifies that the four staging files exist and the validation flag in memory-index.md is true, then archives previous versions, moves the new documents into production, clears the corrections log, and deletes the staging directory.

Archiving previous AI memory files during a memory update cycle involves moving legacy memory documents and dated session extracts into an archive directory to maintain historical context traceability before promoting the newly validated staging documents into production.

Memory promotion fails when the validation flag is not true because the process enforces validation by checking that the flag in memory-index.md is set to true, ensuring only verified memory updates are moved into production.

You cannot finalize an AI memory cycle if the four required staging files do not exist, because the promotion operation enforces a strict check confirming the presence of memory-people, memory-work, memory-context, and memory-index before proceeding.

The best way to clear the corrections log and remove staging artifacts is to run a deterministic memory promotion process that swaps verified documents into production, clears the log, and removes the empty staging folder as the final cleanup step.

You need to archive session extracts during a knowledge management file promotion when finalizing an update cycle, specifically archiving extracts dated on or before the current cycle to keep historical context traceable before clearing the corrections log.