implementation-contract-review-harness

A contract review for coding agents evaluates a planning artifact's scope tightness, ambiguity leakage, and risk coverage before implementation begins. It grounds the plan against repository evidence to prevent scope drift and unsafe execution.

To validate an implementation contract against repository grounding, submit your existing clarification summary to the review harness. It checks whether the artifact's facts map to real repository evidence and flags invented assumptions before returning a single execution readiness verdict.

No, the contract review harness does not rewrite your implementation plan. It acts as a pre-implementation sensor that evaluates ambiguity leakage and approval-required edges, returning exactly one verdict to gate execution readiness.

Yes, you can use contract review for human-in-the-loop approval gates. It identifies approval-required edges and explicitly represents them, returning a contract-needs-user-decision verdict when human intervention is required before implementation starts.

The implementation contract review returns exactly one of four verdicts: contract-approved, contract-needs-tightening, contract-needs-user-decision, or contract-not-safe. These verdicts enforce release gates by verifying scope tightness and risk coverage against repository grounding.

You need to run a pre-implementation contract review when a task already has a planning artifact but requires a second-pass sensor for execution readiness. It is essential when you must verify scope validation and prevent rework from under-specified or ungrounded contracts.