Hi, I'm Ryan , CTO at airCloset. In Part 1 , I wrote about unifying 46 repositories of production code into a single knowledge graph via static analysis. The graph itself got built, but I closed the post with four open issues : no semantic search, node explosion, having to open the file to actually know what a function does, and the cost of writing a new parser every time a new boundary pattern showed up. This Part 2 is about how I solved the first one — the entry-point problem (no sem...