Capability
It traces what else the change affects.
Changes rarely stay where they are made. Using the codebase map, Moonray AI traces outwards from what changed to everything that depends on it, across files and across services, so nobody has to guess whether a small edit matters somewhere else.
What it does
For each part of a change, we walk the map outwards: the direct callers, then theirs, stopping where the effect can no longer plausibly propagate. The result is a list of the things this change reaches, with the ones your tests never touch marked.
It is deliberately framed as what this touches, not as everything that could break. A wrong all clear is more dangerous than no answer, so the trace reports reach, and the assessment reports confidence separately.
What this change reaches
payments-api/refunds.go
ledger.RecordRefund
webhooks.EmitRefunded untested
billing-web /refunds other repository
payments-api/idempotency.go
middleware.Chain
4 call sites, unchanged
Reach, not a guarantee. One reached path has no coverage and is listed as a gap.
Questions.
Does it cross service boundaries?
Within the repository map, yes. Dependencies outside the installed repository are stated as context gaps rather than treated as known.
Is this the same as a dependency graph?
It is built from one, but it is scoped to what this change actually reaches rather than showing you the whole graph and leaving you to find the relevant part.
See it on your own pull requests.
We install on one repository, let Moonray AI assess the next changes your team opens, and go through what it found with you. If the position is not better than what you have now, you will know within a week.
Nothing to host. Reviews begin on the next pull request opened.