rtl-p4s-bugfix-policy

What problem does it solve?

This policy codifies a mandatory, auditable workflow for diagnosing and fixing RTL bugs so teams avoid ad-hoc fixes, missed verification, and inconsistent escalation during the RTL verification phase.

Core Features & Use Cases

• Mandatory 4-step sequence: Enforce analyze → fix+lint → testbench → functional verification per modified module to ensure disciplined progress and traceability.
• Parallel UNIT_FIX decision tree: Define when fixes can run in parallel versus when sequential or integration-first handling is required, with rules for verification-done markers.
• Escalation and checklists: Provide concrete escalation triggers, stop conditions, naming conventions, and a final checklist to satisfy project quality gates and handoffs.
• Use Case: A verification engineer receives a failing test; use the policy to determine required linting rounds, testbench updates, whether to run parallel module fixes, and when to escalate to architects.

Quick Start

Apply the RTL Bug Fix Policy to the failing module by following the mandated analyze, fix and lint, testbench update, and functional verification sequence and record escalation or lesson-learned outcomes.