verification-before-completion

Enforce verification before completion by requiring fresh evidence from verification commands before any success claim. You must run builds, tests, or checks, capture their outputs, and justify completion claims with that evidence before declaring a pull request ready.

Evidence-driven claims validation requires running verification commands and reviewing their actual outputs before stating that code work is successful. This mechanism prevents premature success declarations by ensuring an immutable verification trail documents every check and its result.

Create an audit-friendly verification trail by specifying verification commands, capturing their fresh outputs, and justifying completion claims with that evidence. This process documents an immutable record of all builds and tests checked before success is declared.

Yes, you can use this verification workflow for deployment checks and status reporting. It applies to any process where verification is essential, requiring you to run checks, capture outputs, and validate completion criteria before reporting a successful deployment status.

Claiming success prematurely hurts delivery integrity because it allows unverified code or builds to pass quality assurance. Requiring fresh verification evidence before completion prevents these premature success declarations and maintains an audit-friendly trail of actual test and build outputs.

You should not skip an evidence-driven verification process when completing code reviews, builds, tests, or deployment checks. It is essential whenever status reporting requires proof, though it may be unnecessary for trivial documentation edits that do not impact code execution or build integrity.