Staleness Management

In one line: Treat memory as a claim to verify against its proper source.

1. Identify the subject, revision, environment and observation date where relevant.
2. Verify code claims against code, intent against the exact accepted artifact, and deployment claims against runtime/release evidence.
3. Correct wrong active guidance with a reason and source link. Preserve accepted history and required original evidence.
4. Retain still-valid blockers regardless of age, with owner, source and last review.
5. Retire a design through its authorized decision process—not because the feature shipped.
6. Verify any host reminder or retrieval-exclusion mechanism before relying on it. Size checks and dates do not establish factual freshness.

The detailed procedure and examples are in Appendix D; optional generated repository snapshots are covered in Appendix J.

---