μArch-to-Verify Policy (Phase 4→5)

What it does

This policy document codifies the Phase 4→5 transition rules for RTL implementation and verification: artifact gates (required files and smoke tests), quality gates (functional coverage, lint, traceability), retry policies, feedback-loop classifications, and failure escalation. It provides the checklist and state conventions needed to automate or audit phase transitions in a hardware verification pipeline.

When to use it

Use when orchestrating or reviewing RTL→Verification handoffs: gating releases from implementation to verification, running automated checks before phase transitions, enforcing coding and naming conventions, or when classifying and handling feedback loops that arise during verification. It's a reference for reviewer agents and pipeline orchestrators.

What's included

• Scripts: none bundled; purely a reference and policy artifact
• References: detailed phase gate definitions, validation rules, and feedback loop schemas
• Instructions: intake checklists, artifact and quality gate criteria, sub-phase re-entry rules, and lessons-learned recording format.

Compatible agents

Best used by CI/orchestration agents, verification reviewer agents, and developer-facing bots that enforce gate checks, collect evidence, and escalate policy violations to humans.