H.2.3 Knowledge Lifecycle

Repository knowledge needs a lifecycle just as code does.

• Put the supported contract, representative example, owner, and deprecation state close to the surface they describe.
• Version or supersede decision records so a search result shows whether its rationale still governs the current state.
• Detect stale documentation through changed APIs, dead links, failed examples, repeated questions, and support incidents.
• Archive or redirect retired knowledge while preserving audit context that still matters.
• Measure whether people find the right contract and owner, not only search latency.