confirm-complete

Evidence-backed completion blocks code landings until tests pass, builds succeed, and security scans complete. It guides verification through a structured workflow with quality gates and end-to-end checks to prevent premature or unreliable software delivery.

End-to-end verification validates that completion claims are backed by executed evidence. The process requires passing tests, successful builds, completed security scans, and spec coverage audits before transitioning to land changes.

Quality gates block land-changes by requiring executed evidence at each verification step. You run the verification workflow and attach required evidence, ensuring tests, builds, and security scans succeed before claiming completion.

Yes, spec coverage audits are part of the end-to-end verification process. They satisfy requirements for mandatory evidence capture, ensuring completion claims are fully backed by auditable proof during code reviews and feature landings.

Evidence-backed verification is not suitable for rapid prototyping or exploratory work where auditability is not required. It is designed for software delivery pipelines and feature landings where preventing unreliable delivery is critical.