validate-gates

To verify quality gates after code implementation, you need a second-pass audit that detects skipped gates, missing evidence, and self-reported passes without proof. This validator audits the quality_gates artifact produced by an implement run to surface evidence gaps.

A post-implementation quality gate audit is a verification process that checks governance outputs for completeness. It detects missing evidence by validating that the output includes evidence references and flags self-reported passes that lack corresponding proof.

To check for self-reported passes without proof in a CI pipeline, run a validation step after implementation. This process flags inflated success claims by cross-referencing governance rules against the actual evidence references provided in the quality_gates output.

Yes, you can use a quality gate validator to align code review outputs with governance rules. It audits the implementation artifacts to ensure they adhere to predefined governance standards and validates that all required evidence is present for downstream verification.

Relying on self-reported quality gates during software governance reviews risks auditability gaps due to skipped gates, missing evidence, and unverified success claims. A second-pass validation is required to ensure the output aligns with governance rules and supports downstream verification.