verification-before-completion

Verify code changes before claiming completion by mapping the exact assertion to specific, fresh evidence and inspecting command outputs with exit codes. This process downgrades outcomes to unverified if the collected evidence fails to prove the claim.

Evidence-based verification for release readiness is a process that requires collecting fresh, claim-specific proof before declaring success. It prevents premature completion claims by demanding new test runs or inspections rather than relying on assumptions or stale CI logs.

Prevent false completion claims during debugging by forcing an evidence-first completion gate that requires running new checks and reading command outputs. It downgrades any fix to unverified if the exact claim lacks fresh, supporting proof.

Yes, this verification approach escalates for multi-module changes. It increases verification effort for higher-risk modifications spanning multiple files, agents, security configurations, or migrations to ensure broad changes are thoroughly proven before completion.

Structure an audit trail for testing results by generating a consistent evidence checklist. This checklist records the specific claim, evidence source, command inspection, output result, and whether the outcome is verified or unverified.

You should not rely on stale logs for CI verification when asserting that work is fixed, passing, or ready. This approach requires fresh evidence collection and correct inspection of exit codes to prove the exact claim before completion.