verification-before-completion

To enforce verification evidence before marking a pull request complete, you implement a formal verification gate that requires executing verification commands, capturing their outputs, and attaching those results as evidence. This precludes premature completion claims by ensuring fresh evidence is documented before any success assertion.

An evidence-first protocol for code reviews requires running explicit verification commands and documenting the captured outputs as auditable evidence. This ensures task handoffs and completion claims are backed by fresh verification results, maintaining integrity across development workflows.

To stop premature completion claims during software development, you enforce a verification gate that precludes success assertions until fresh verification evidence is available. This requires executing verification commands and capturing outputs before any task handoff or pull request submission.

Yes, you can use a verification gate for data work and project tasks outside of code reviews because it is widely applicable to any work requiring auditable completion. You execute verification commands, capture outputs, and document results as verifiable evidence before claiming success.

The best way to document verification results for auditable task completion is to execute explicit verification commands, capture their outputs, and attach those results as evidence to pull requests or handoffs. This evidence-first protocol ensures work is only considered done when fresh verification is available.

You need to run fresh verification commands before claiming task success because stale or assumed results break integrity across development workflows. Requiring fresh execution and captured outputs precludes premature completion claims and ensures your success assertion is backed by verifiable evidence.