Know what your change could break before it ships.
code review
Identifies breakage beyond a change’s diff and proves its key safety fact by running real code.
When to use it
Use when assessing a change’s blast radius, investigating possible breakage, or reviewing a suspicious small diff.
Give it a change in a project; it returns a blast-radius assessment whose central safety fact is proven or marked unproven.
What you provide
No additional actions listed in the analysis.
Requires the final writeup to be written through unslop.
Routes pulling the PR and commits to why step 2; whether why is always required is unstated.
Uses arena for big or wide changes so several models can assess the same question.