How pure are these codebases? When do they break their own conventions and why? Key finding: purity inversely correlates with size. Ecto has 0 TODOs; CockroachDB has 1,048. Neither is wrong — they're different kinds of systems.
Four documents examining codebases at module and ecosystem levels: - architectural-analysis.md — internal structure, dependency flow - ecosystem-analysis.md — consumer extension points, deliberate absences - crosscutting-analysis.md — logging, config, retry, lifecycle - testing-evolution-analysis.md — proof models, API evolution strategies
Rodin