pelizzai-verification-before-completion

Evidence-based verification requires generating fresh, observable proof such as test outputs or build logs after the final code mutation. This strict verification gate links specific code mutations to their corresponding test or build outputs before any task completion claim is made.

Verification evidence for bug fixes and refactoring requires running characterization tests before and after the change. This confirms behavior remains identical and provides observable proof that the code mutation achieved the intended technical accuracy.

A verification matrix provides a structured framework to determine the appropriate proof type for different tasks. It matches specific development phases like UI changes or infrastructure updates with their required observable evidence, ensuring technical accuracy and reliability.

Yes, the verification gate applies to all development phases including UI updates and final delivery. It mandates that visual verification or build logs must be generated after the final code mutation before declaring the work complete.

Fresh observable evidence is needed for work completion claims to prevent the pitfall of asserting success without actual proof. Causality-based validation links specific code mutations to their corresponding test or build outputs, ensuring technical accuracy and reliability.

The best way to validate code mutations during quality assurance is to run the required test suite and confirm the output. This causality-based validation ensures that fresh, observable evidence is generated after the final code mutation before declaring the work complete.