verification-before-completion

Verify completion claims by identifying a proving command, executing a full run, reading complete outputs and exit codes, and confirming results match the claim. This evidence-based verification prevents misleading stakeholders and ensures reproducible reporting.

Evidence-based verification requires running explicit commands like tests, builds, and lint checks to produce concrete outputs before claiming success. It ensures transparent, reproducible reporting and prevents unvalidated completion status across development pipelines.

Enforce a verification gate by identifying the proving command, running the full command, reviewing the complete output and exit code, and verifying results against the claim. Only assert completion with clear, fresh evidence.

Yes, this verification approach applies to software development, testing, CI pipelines, code reviews, and release readiness. It requires explicit verification steps and evidence before asserting success, ensuring honest and traceable completion.

You need fresh verification outputs when completion status must be validated with concrete evidence. Claiming completion without fresh verification misleads stakeholders and hides underlying defects in AI-assisted workflows.

Asserting completion without explicit verification commands lacks traceability and reproducibility. Without running fresh tests, builds, or lint checks and reviewing exit codes, underlying defects remain hidden and completion claims are unvalidated.