The final signoff package is the file that lets a stranger, months later, reconstruct exactly why the chip was declared RDC-closed. It contains evidence, not conclusions: every verdict points at the run, revision, or record that backs it. If an item cannot point at evidence, it is not done.
Item | Contents |
|---|---|
Reset intent | The frozen revision: every reset, domain, and release rank, with review sign-off. |
Structural reports | Final-RTL runs with final intent, showing zero open defects, plus the full finding list with dispositions. |
Waiver records | Each waiver with its finding, argument, evidence, approver, and expiry; none expired. |
Dynamic-check results | Reset-aware test and assertion results on final RTL, with seeds and configurations. |
Coverage summary | The coverage questions with their holes closed or explicitly dispositioned. |
Review minutes | Per-domain verdicts, action lists with owners, and evidence pointers with revisions. |
Change-delta statement | Every change since the last clean run listed with its re-check evidence. |
IP reset contracts | The completed checklist per third-party and reused IP instance. |
A reviewer samples the package backwards: pick a verdict, follow its pointer, confirm the evidence exists and matches the final RTL. One broken pointer fails the package, because a verdict without reachable evidence is an opinion. The package passes when every sampled verdict resolves to current evidence and every checklist row is present with its revision named.
Not complete. Without seeds and revisions the results cannot be reproduced or matched to the final RTL, so the dynamic-check row is an opinion, not evidence.
Not on sampling alone. Sampling builds confidence, but the package passes only when every checklist row is present with named revisions; sampling never replaces completeness.