You have the repository. Now you own the next change.

An old workaround may still protect a customer requirement—or it may no longer be needed. The new maintainer has to distinguish the two before touching it. Files alone do not settle that question.

AKDB now has a controlled route for an authorised human owner to preview and register an existing decision document. Different content requires an explicit version check rather than a silent overwrite. That records what was adopted, not whether the decision is correct. AI cannot supply missing history as fact.

A possible evaluation would focus on one system and a small set of decisions the new maintainer needs to understand. Agreed notes and source snapshots would provide the material; the successor would check whether the retrieved context answers the actual questions.

Record where the successor still needs help, which information is outdated and how much effort the handover takes. This is an adjacent application to explore, not a packaged knowledge-transfer service or an automatic recording of conversations.