GitNexus

gitnexus turns git history into a queryable graph: co-change relationships, per-file change frequency, and the historical blast radius of a path. It is the evidence source for "do changes actually stay inside the intended boundary?" and a corroborating signal for the volatility axis of Balanced Coupling — domain role sets volatility; churn only supports it, it never sets it.

Evidence dimension: change.

When to use

Use to score change_locality (do edits respect module boundaries over history), to ground volatility claims, and to find fragile seams where distant modules co-change repeatedly. A module that churns and co-changes with a distant module is a coupling risk only history can show. Build the index during the system-map step.

Commands