verification-before-completion

To enforce verification before completion, implement a strict gate function requiring fresh test execution output as evidence before any success assertion is made. This prevents premature claims by mandating that commands are run and results observed during CI/CD pipelines.

An evidence-based assertion protocol for code quality ensures that claims of builds succeeding or bugs being fixed are always substantiated by freshly executed verification commands, preventing the shipping of incomplete or broken code.

To verify bug fixes, run the relevant test command, observe its output, and confirm it passes. You must execute this fresh verification step rather than assuming the fix is complete after making the code change.

Yes, this verification protocol works without external dependencies. It functions as a mandatory process gate requiring no specific frameworks, ensuring adherence to evidence-based assertions across all development stages.

You should not bypass the evidence before claims verification gate when a task is marked complete. It is strictly designed to prevent assuming success after code changes, requiring fresh test execution output for every completion assertion.