blast-radius

# Blast radius Find what a change breaks somewhere else, before it ships. Use for "blast radius of X", "what could this break", or reviewing a small diff you don't trust yet. Companion to `how` and `why`. `how` tells you what the code does. `why` tells you why it's shaped that way. Blast radius tells you what it breaks somewhere else. Listing the callers is not the job. The agent can grep those in a second. The job is the breakage grep won't show you. ## Don't trust your own writeup A blast-radius writeup that sounds right is worthless. It reads as convincing whether or not it's true, and that is the trap you are walking into. So don't hand back the writeup. Find the one or two facts the whole thing depends on and prove them by running code. Words are where you start, not what you ship. ### How sure are you For each fact the change's safety depends on, get it as far down this list as is cheap, and say where it stopped. 1. You said so. Worthless on its own. 2. You pointed at the line. A real `file:line`, or the library's own source. 3. You showed the bad case can't happen. You walked the failure step by step and it doesn't reach. 4. You ran it. A script or test that calls the real code and fails loud if you're wrong. 5. You reproduced it in the running app. Any safety fact you can't get to step 4, say so out loud. Don't write it up as settled. Step 4 is usually one small script that imports the same library the app ships and calls the exact function you're worried abo...