verification-before-completion

Verification before completion prevents premature status claims by requiring fresh validation evidence prior to committing code. It enforces evidence-based status reporting by validating full command output and exit status to confirm task completion in software workflows.

You validate completion by running a verification command, recording its full output, and checking exit codes for any failures. Completion is only reported when this evidence validates the outcome and confirms all reproducibility conditions are met.

Yes, verification before completion suits code reviews, CI/CD pipelines, and release workflows where accurate status signals matter. It enforces running a defined verification command and validates full output to ensure evidence-based confirmation.

The best way to ensure evidence-based status reporting is to run a defined verification command and record its full output. Validate the exit status and check for failures so that completion is only reported when evidence validates the outcome.

Your pipeline reports completion prematurely because it lacks a verification step that records command output and checks exit codes. Enforcing a verification command prior to any completion claim ensures evidence validates the outcome and prevents dishonest status reporting.

Yes, you need to define a specific testing or validation command that proves completion. The process requires running this command, recording its full output, and checking its exit status to confirm all conditions are met before reporting.