verification-before-completion

Evidence-based verification requires running a fresh verification command, reading its outputs, and validating exit codes before reporting completion. A gate-driven process prevents premature success claims by withholding task closure until verifiable logs and results are attached as evidence.

Gate-based verification is a workflow mechanism that blocks completion claims until a verification command is executed fully and its outputs are validated. It acts as a quality-assurance gate, ensuring no task closes without fresh, attached evidence confirming the results.

To stop misleading success claims in pull requests and releases, enforce a standard verification workflow that requires running validation commands and attaching fresh outputs, logs, and exit codes before any completion or deployment is reported.

Yes, gate-driven verification applies directly to software development workflows, QA processes, and task closures. It identifies the required verification command, executes it fully, verifies the outputs, and only then permits success reporting for any of these contexts.

Attaching verifiable outputs requires running the verification command fully, capturing the resulting logs and exit codes, and validating the results before reporting. This evidence-first approach ensures all completion claims are backed by fresh command outputs.

Relying on manual checks risks misrepresentation in pull requests and releases because it lacks a standard verification workflow. Without a gate-driven process enforcing fresh command execution and output validation, teams may report premature or misleading completion claims.