Change Coupling
Which files repeatedly change together? A sensor of hidden coupling — the repository itself becomes a sensor, no code reading required.
Change coupling reveals relationships the dependency graph can’t see: modules that have no structural dependency but always change together. This is often a sign of shared business rules, duplicated logic, or implicit coordination.
Sensor properties
| Property | Value |
|---|---|
| Oracle strength | Medium — coupling correlates with risk |
| Independence | High — computed from git history |
| Scope | System-level |
| Feedback latency | Days |
| Actionability | Exploratory — shows the coupling clusters |
| Type | Retrospective |
What it cannot detect
Change coupling shows correlation, not causation. Files that change together may do so for coincidental reasons (same sprint, same author) rather than structural coupling.