The Change Conductor: coordinating a safe cross-repo refactor

Renaming a shared endpoint means touching every repo that calls it, in the right order, without breaking anyone mid-flight. That coordination is where cross-repo changes go wrong.

The Change Conductor builds the plan for you from the org graph: update the provider first, then each consumer repo in dependency order (most-affected first) with the exact call sites, then tests, then verify. It attaches the pillar gates as merge conditions — the provider stays blocked until the consumers are green.

On the Living System Map, hit Simulate & conduct this change and the impacted services glow — a dry run of the blast before a line of code is written. Auto-opening the coordinated PRs and self-verifying the caller patches are next on the roadmap; today it gives you the plan and the map.