The rotation example lands well because the requirement that the old secret stops working after the window is exactly the line a passing test suite won't notice is missing. Splitting author, runner, reviewer and deployer into four written decisions helps even when two people hold all of them. The column for what each role never needs, like production secrets for the runner, is a detail more teams should copy.
StackShortlist
Proof Over Promises.
The rotation example lands well because the requirement that the old secret stops working after the window is exactly the line a passing test suite won't notice is missing. Splitting author, runner, reviewer and deployer into four written decisions helps even when two people hold all of them. The column for what each role never needs, like production secrets for the runner, is a detail more teams should copy.