What the project knows, and who holds it
Workspace
Every answer comes with the graph path it rests on. Click a module in the graph to ask who knows it.
The most central code
Ask the repo
Who knows and who merges a module, why code is the way it is, which docs drifted, who should take an issue.
Exit interview
How much important, unwritten knowledge leaves with them, then the questions that recover the most of it first. Answers are written back into the graph.
What if
Runs on a GRAPH.COPY fork that is deleted afterwards. The real graph is never touched.
Who holds it
KNOWS is a time-decayed score from authoring, reviewing and commenting. It halves in about eight months without touching the code.
Evidence
Each test forks the graph, deletes everything after a cut-off date, re-derives KNOWS as of that day and checks the prediction against what really happened.