Building One Knowledge Graph Across 46 Repositories With Static Analysis (Part 1) (opens in new tab)

Hi, I'm Ryan, CTO at airCloset. This post is about unifying a production codebase spanning 46 repositories across multiple services into one knowledge graph, using static analysis. Internally we call it code-graph, and I built it between January and March of this year. Three things I want to write down: Why "just letting AI read the code" isn't enough, and why I had to chase down the connections that cross repository boundaries How I extracted boundaries across 46 repos and a zoo of framework...