verification-before-completion

Verifying code changes before claiming completion requires running fresh verification commands, capturing complete outputs, validating exit codes, and reporting actual status with evidence. This enforces proof of completion and prevents unverified claims in CI pipelines.

Evidence-based verification in software engineering is a disciplined process requiring fresh command execution and output citation before asserting success. It eliminates premature completion claims by ensuring developers validate results against expected outcomes.

Preventing premature completion claims during PR reviews requires enforcing a verification process where fresh commands are executed, outputs are parsed, and exit codes are validated. Actual status must be reported with evidence before marking work as done.

Yes, evidence-based verification works for task handoffs in software development by ensuring auditable proof of completion. It requires running verification commands, checking exit codes, and citing actual outputs before transferring work between developers or pipeline stages.

The best way to enforce verification before marking work as done is to mandate running full verification commands, interpreting complete outputs, and validating exit codes against expected results. This ensures all success claims are backed by fresh evidence.

Requiring fresh command execution prevents unverified completion claims because it eliminates reliance on stale results. By forcing developers to run verification commands and cite current outputs, it ensures success assertions are backed by auditable, up-to-date evidence.