verification-before-completion

A verification gate prevents premature completion claims by mandating the execution of predefined verification commands and evaluating their exit codes before allowing any success statements. This process ensures all claims are backed by fresh, reproducible evidence.

Evidence-based verification in QA cycles and code reviews is a governance process that requires running verification commands and parsing their outputs to assert results. It prevents false completion claims by ensuring success statements are only made after fresh evidence supports them.

You can enforce fresh verification evidence before PR submissions by implementing a gate process that runs verification commands, parses outputs, and evaluates exit codes. The workflow reports evidence-based results, blocking completion claims until reproducible outputs validate the work.

Yes, the verification gate process works without external dependencies. It operates by directly running verification commands, parsing their outputs, and evaluating exit codes to report evidence-based results, ensuring quality assurance without requiring additional framework integrations.

You need to run verification commands for process governance claims whenever marking work as complete in software development, QA cycles, code reviews, or PR submissions. The gate requires fresh verification evidence to prevent false success statements and ensure quality assurance.