context-curation-base

To prevent context bloat after retrospectives, apply a fold-and-archive workflow that extracts persistent data into addendums, folds them into main docs, and archives outdated material. This keeps project references tidy and actionable.

The fold-before-archive workflow extracts persistent data from retrospectives into addendums, folds those addendums into main project docs, and then archives outdated material using layer-based retention rules to maintain reference hygiene.

You extract persistent data from retrospectives by generating addendums after planning cycles, updating your reference docs with this extracted state, and folding the addendums into the main documentation for quick recall.

You should run context curation after completing weekly or monthly retrospectives and planning cycles. This timing ensures outdated material is archived and reference docs are updated before the next iteration begins.

Layer-based retention rules govern how outdated material is archived during context curation. They ensure essential data is preserved through addendum generation and reference doc updates before older project context is fully archived.

Automated context cleanup targets dailies after a retro and planning cycle. It reviews daily logs to generate addendums and fold persistent information into main docs, rather than processing logs in isolation.