specdo-verification

Gate verification for task completion requires a resolved active apply payload and a concrete completion claim. It validates the claim against wrapper rules, ensuring the latest gate history and evidence match the current diff identity before producing a ready verification gate event.

A verification gate is a machine-verified checkpoint that ensures only complete and verifiable apply payloads can proceed with lifecycle actions. It prevents unauthorized progression by validating completion claims, gate history, and code-review evidence prior to task completion, sync, or archive readiness.

You detect stale or missing verification payloads by validating the claim against wrapper rules and ensuring the latest gate history and evidence match the current diff identity. If verification fails, the system hands off to debugging instead of producing a ready verification gate event.

You need to run lifecycle verification checks when a change participates in the SpecDo lifecycle and requires formal verification prior to routing to apply. Run the verification step after you have a complete apply payload to gate the next lifecycle action.

When verification fails during the gate check, the system hands off to debugging. It detects stale or missing verification payloads and prevents unauthorized progression by validating gate history, code-review evidence, and debugging evidence against the resolved apply payload.

Yes, you can use automated verification gates for sync readiness checks. The gate requires a resolved active apply payload and a concrete completion claim, validating evidence to ensure only verified changes proceed to sync readiness or archive readiness.