Lock the correctness criteria before the implementation
Writing the judgment criteria down before handing work to a code generation tool, demoting code, screens, and reviewer opinions to evidence, and stopping when confidence runs out
- Restricting the source of correctness to people and approved specs removes the failure of mistaking the implementation for the spec
- Moving the definition of done past "tests pass" removes any incentive to loosen assertions