verification-before-completion

Evidence-based verification requires running fresh verification commands, checking exit statuses, and recording explicit outputs before declaring completion. This prevents premature success claims by capturing command outputs and relevant logs as audit-friendly proof.

Capture verification evidence by running the full verification workflow and attaching fresh command outputs, exit codes, and logs. This evidence-first workflow supports audit-friendly code reviews and prevents unreliable results from unverified claims.

Evidence-based verification in quality assurance requires running fresh verification commands, inspecting outputs, and recording evidence before allowing success claims. It enforces structured verification gates to prevent unreliable results and eroded trust.

Prevent premature completion claims by enforcing structured verification gates that require fresh output, exit status checks, and explicit evidence recording. This ensures all development, testing, and release activities are validated before success is declared.

Yes, verification before completion operates without external dependencies. It functions as an advanced standalone policy framework to enforce requirements like fresh output and exit status checks for audit-friendly code reviews and continuous integration workflows.