rtl-block-interface-policy

To prevent RTL interface drift during parallel block development, enforce frozen interface contracts using hash-based verification at merge points and strict naming conventions for shared package files. This locks timing and interface definitions across Phase 2 through Phase 4 workflows.

A timing contract in RTL design is an embedded block specifying timing requirements within an interface file. It is needed during Phase 2 through Phase 4 parallel block development to lock microarchitecture timing and prevent integration mismatches at merge points.

Verify a frozen RTL interface at merge time by running a hash-based verification command that detects freeze violations. This checks shared interface artifacts against their declared Phase 2 exit state to ensure no unauthorized changes occurred during parallel development.

Handle needed interface changes after an RTL freeze by following a multi-step escalation protocol involving worker, coordinator, and leader roles. A block worker detects the needed change during Phase 4 and requests a coordinated update through this defined hierarchy.

Yes, the interface policy defines valid-ready handshake, backpressure, and multi-beat transfer rules. It establishes these protocols alongside naming conventions and timing contract formats to ensure robust cross-block communication in parallel RTL development.