compound-refresh

To prevent documentation drift, review knowledge base entries against current code and architecture reality. This process classifies each entry as keep, update, consolidate, replace, or delete using evidence instead of guesswork.

Deduplicating stale learnings requires an evidence-first review that identifies overlapping entries and consolidates them. This ensures shipped work supersedes contradicted guidance while maintaining an accurate library.

Reviewing compound learnings against repository reality involves evaluating docs/compound entries using evidence-first classification. You classify each reviewed item as keep, update, consolidate, replace, delete, or mark it stale when confidence is low.

Yes, you can run the review in propose mode to generate recommendations without modifying files. This controlled change application reports suggested actions for updating, consolidating, replacing, or archiving entries supported by evidence.

Yes, the workflow produces a timestamped refresh report in the docs/closure directory. This accountable report summarizes the gathered evidence, actions taken, and necessary follow-ups for future reference.

You should mark a knowledge base entry as stale when confidence is low during the evidence review. This flags overlapping or outdated guidance for future consolidation rather than permanently deleting potentially useful information.