Cross-repo blast radius: the thing single-repo tools can't do

Ask a single-repo linter what a change breaks and it can only look inside the current repo. But the caller that breaks usually lives somewhere else.

Impact holds the cross-repo dependency graph, so it can answer the real question: if I change this service's API, what breaks?

Select a service on the Living System Map and you get its blast radius: the other services that consume its endpoints, how many endpoints are exposed, and every call site (project, file, line) that would break. Flag them in the PR — not on launch day.

"Your change to auth-svc breaks 3 endpoints in web and mobile." That sentence is the whole pitch, and no single-repo tool can say it.

This is the foundation the Change Conductor and Contract Drift both build on.