implementation-readiness-gate

An implementation readiness gate consolidates clarification evidence and contract review verdicts into a single execution decision. It validates scope, resolves ambiguity, and returns exactly go, go-with-caveats, or no-go to prevent starting implementation with weak artifacts.

An implementation gate is a pre-coding checkpoint that applies checklist-based validation to scope and ambiguity resolution. It reviews clarification summaries and optional contract verdicts to produce a single workflow decision without changing the underlying artifact strength.

A readiness gate flags missing or contradictory inputs as conservative safety constraints. It does not override negative review evidence and ensures caveats are not hidden inside a go decision, requiring artifacts to be strengthened before safe progress can proceed.

Repository validation awareness ensures the validation plan is linked to real repository mechanisms rather than generic placeholders. This checklist-based validation confirms that scope and ambiguity resolution are backed by actual repository mechanisms before returning a workflow decision.

Yes, the gate applies to cases with partial or contradictory artifacts. It consolidates available clarification summaries and optional contract review verdicts, returning go-with-caveats when evidence is sufficient but incomplete, or no-go when risks require explicit approval edges.

You should not use it when implementation can safely proceed without explicit approval edges or when task evidence is unambiguous and complete. The gate targets pre-coding stages where tasks are ambiguous, risks require approval, or artifacts may be partial or contradictory.