retire-memory-bank

To archive memory bank documentation without losing historical context, you identify retirement candidates, draft a retirement notice, archive original docs under memory-bank/archived/[year]/[topic]/, and update cross-references. This preserves traceability and maintains an auditable timeline for future researchers.

The best way to retire outdated knowledge management entries is to follow a structured retirement workflow that documents rationale, extracts lessons, and creates a clear migration path. This links current and archived documentation, ensuring future discoverability and minimizing confusion.

You add deprecation notices to production documentation during archiving by updating the active docs with guidance and links to current solutions. This minimizes confusion for users while the original entries are moved to the memory-bank/archived/ directory structure.

You should retire memory bank entries when they are outdated but still hold historical context or lessons worth preserving. Retiring them moves the original documentation to an archive with cross-references rather than deleting it, maintaining an auditable timeline for researchers.

Yes, you can maintain cross-references between archived and current documentation. The process links retired entries to current solutions and creates a clear migration path, ensuring traceability and future discoverability across the memory bank structure.

You organize archived knowledge for future research by placing it under memory-bank/archived/[year]/[topic]/ with a complete retrospective. This structured directory organization, combined with documented rationale and cross-references, ensures researchers can easily trace historical context.