cross-phase-contract-validator

Cross-phase contract validation checks port widths, memory classifications, pipeline depth, and bus parameterization across P3 uarch specs, P4 RTL implementations, and P5 verification contracts to prevent silent inconsistencies during phase handoffs.

You can verify REQ traceability by running validation checks that enforce requirements are implemented and traceable to RTL artifacts across the P3→P4 and P4→P5 boundaries, catching mismatches before integration and verification phases.

Run cross-phase validation at the P3→P4 boundary to check port widths and bus parameterization against uarch specs, generating a report that identifies mismatches before proceeding to RTL integration or verification phases.

You need to revalidate cross-phase contracts after RTL changes and bug fixes to catch regressions, ensuring that modifications to P4 RTL implementations still comply with upstream P3 uarch specs and downstream P5 verification contracts.

Yes, cross-phase contract validation applies at the P4→P5 boundary before verification, checking that RTL implementations align with verification contracts across port widths, memory classifications, pipeline depth, and bus parameterization.

Cross-phase contract validation focuses on P3, P4, and P5 artifact consistency including port widths, memory classifications, pipeline depth, and bus parameterization, but does not replace functional simulation or full verification of RTL behavior.