Blast radius

Find the breakage a diff can cause beyond the files it touches. The result is useful only when its key safety claims are supported by code, an executable check, or a clearly named evidence gap.

Use how to trace runtime behavior and why to recover historical constraints when those branches matter.

Proof ladder

Take each safety-critical claim as far down this ladder as the repository and available tools allow:

1. Assertion. A plausible statement with no evidence.
2. Source. A concrete file:line, pinned dependency source, schema, or protocol definition.
3. Trace. A step-by-step path showing whether the failure can reach an affected boundary.
4. Executable check. A script or test that calls the production path and fails when the claim is false.
5. Runtime reproduction. The behavior reproduced in the running system.

Treat levels 1 and 2 as leads. Mark a safety-critical claim unproven when it cannot reach level 4, and explain what prevented stronger proof.

Workflow