verification-before-completion

To enforce evidence-based verification, you must run deterministic validation commands and collect their outputs and exit codes before claiming completion. This ensures every success assertion is backed by fresh, verifiable execution results.

Running verification commands before a pull request prevents unverified completion claims by enforcing evidence-based validation. It requires running deterministic checks and capturing outputs to ensure only validated changes are merged.

The best way to validate completion claims during releases is to enforce an evidence-driven checklist that executes deterministic verification commands, collects outputs, and mandates reporting verifiable evidence before concluding success.

To collect and report verification evidence, execute your validation commands and aggregate the outputs, exit codes, and logs into a centralized summary. This provides concrete, auditable proof required before finalizing a completion claim.

Yes, evidence-based validation works without external dependencies by enforcing the execution of existing deterministic verification commands within your environment, requiring only that outputs and exit codes be collected and reported as proof.

Claiming completion without fresh verification evidence violates the core principle of evidence-driven validation. You must instead record the missing evidence and attach outputs, exit codes, and logs for review before concluding success.