codebase knowledge graphs

How do you keep a codebase knowledge graph from going stale?

We're considering a knowledge graph to preserve the reasoning behind code, using history and review discussions as sources. It sounds useful for onboarding and refactoring, but how do…