verification-before-completion

To enforce verification before claiming a pull request is complete, run full verification commands, review the fresh output logs, and only declare success if the results pass. This structured process prevents unverified success by requiring evidence-based assertions.

The step-by-step process for software deployment verification involves identifying the command, running the full verification, reading the outputs, verifying the results, and only then claiming completion with all evidence attached. This enforces a strict quality-assurance gate.

You attach fresh test results as evidence for development milestones by running the required verification commands and capturing the output logs immediately before claiming completion. This ensures all assertions are supported by newly generated proof rather than assumed success.

Claiming completion without verification leads to unreliable software results because it allows unproven outcomes to propagate through deployment checks. Enforcing a verification gate with fresh outputs prevents misinformation by ensuring every success claim is backed by concrete logs.

You cannot use automated checks for pull requests without attaching evidence if you follow this verification process. It strictly enforces that all PR-checks must be run, outputs read, and results verified with fresh logs before any completion status is asserted.