I mapped LangChain Core as a knowledge graph — here's what the structure reveals

I mapped LangChain Core as a knowledge graph. 180 modules, 650 dependency edges. Here's what the structure reveals that the docs never tell you. Finding 1: The messages module has a 70% blast radius. Change it and 126 of 180 modules break — directly or transitively. Every callback, every agent, every retriever, every embedding module traces a dependency path back to messages. It is the load-bearing wall of the entire framework. Nothing in the documentation flags this. Finding 2: runnables.base r