verification-before-completion

Prevent premature completion claims by requiring fresh verification evidence before any status updates or releases. This approach enforces evidence-based status reporting, ensuring code quality claims are backed by actual verification command outputs rather than assumptions.

Evidence-based status reporting is a software process guardrail that requires running fresh verification commands, reading their outputs, and reporting completion status only after the evidence supports the claim. It maintains quality and trust by providing auditable references.

Set up verification workflows by applying gate-and-verify requirements across Normal, Autopilot, and Full-auto modes. Each mode has corresponding command behavior with guardrails and escalation paths, requiring you to identify the verification command, run it fresh, and read outputs before reporting.

Yes, you can use automated verification to gate pull requests by requiring fresh verification evidence before PRs are created. The process identifies the verification command, runs it fresh, reads outputs, and only allows completion claims when evidence supports them.

Automation workflows report completion without verification when gate-and-verify requirements are not enforced. Requiring fresh verification evidence, running the verification command, and reading its outputs before status updates prevents these premature completion claims.