Blast radius

Find what a change can break beyond its diff. Listing callers is reconnaissance, not the result. The result is the one fact the change is safe because of, proven as directly as practical.

Contract

• Fixed point: review the requested base through current working state unless the caller supplies another point.
• Fence: inspect non-local contracts and run verification; do not edit product code.
• Question: what hidden consumer, lifecycle, wire shape, shared state, or external contract can turn this change into a defect?

Proof ladder

Move each safety fact down this ladder as cheaply as possible: source line -> walked counterexample -> executable script or test -> real running entrypoint. A claim below executable proof is unproven, not safe by confidence.

Pass