verification-recheck-policy

What problem does it solve?

Ensures reviewers and engineers run the appropriate minimum set of verification activities after code review or refactor work so that style, functional, CDC, synthesis, and equivalence risks are neither under- nor over-checked and that failures are reproducible and escalated properly.

Core Features & Use Cases

• Change-type matrix: Maps change categories (style-only, logic refactor, interface-impact, constraint/synthesis-impact) to the minimum verification activities required.
• Pass/fail and escalation rules: Defines clear criteria for lint, CDC, functional/regression, synthesis/timing, and equivalence checks and when to escalate.
• Operational guidance: Provides recommended open-source commands and replay guidance to generate reproducible artifacts for audits and debugging.
• Use case: After an interface-impact change, quickly determine the required CDC, functional regression, and equivalence checks and produce a recheck report with artifacts for design owners.

Quick Start

Generate a verification recheck matrix for an interface-impact change that lists required lint, CDC, functional regression, synthesis/timing rerun, equivalence checks, pass/fail criteria, and escalation steps.