What problem does it solve? It helps architects and developers determine whether modules in a codebase are too tightly coupled, why changes cascade unexpectedly across modules, and which integrations should be refactored to reduce maintenance cost. ## Core Features & Use Cases - Three-Dimensional Coupling Model: Classifies each dependency by integration strength (intrusive, functional, model, contract), physical distance, and volatility based on Vlad Khononov's framework. - Dependency Graph Mapping: Builds a directed module dependency graph and computes distance via the encapsulation hierarchy, including Conway's Law adjustments for cross-team ownership. - Prioritized Health Report: Produces an executive summary, annotated dependency map, severity-ranked issues with code evidence, and actionable refactoring recommendations. - Use Case: Ask why changing a pricing rule requires deploying three services at once; the analysis identifies symmetric functional coupling across services and recommends extracting shared logic into a dedicated module. ## Quick Start Analyze the coupling between the modules in this repository and produce a coupling report with prioritized recommendations.
