Restate supported modes, parameters, performance, and exclusions.
Walk requirement-to-evidence traceability.
Review the worst functional, CDC, timing, power, DFT, and reliability risks.
Open every waiver with owner, rationale, evidence, expiry, and impact.
Show reproducible report revisions and unresolved issue disposition.
Record approve, conditional approve, or reject with named actions.
The review closes the same resilient streaming peripheral introduced at the hub. It does not substitute generic checklists for evidence: each claim points to a specification row, test or assertion, implementation report, and named owner.
For CP-1, release remains pending until the learner supplies the integrated design/harness and fresh evidence for CP-CTRL through CP-PROGRESS. The filled baseline and traces are a design/review starting point, not completed hardware. Example decision: reject release if functional conservation passes but the held-data arrival bound is absent, a reset epoch remains unresolved, or measured no-stall latency exceeds 24 IO periods; assign a named correction and rerun affected evidence.
Copy this table into the review package. One row per requirement; a row with an empty evidence cell blocks approval.
Requirement | Evidence (test, assertion or report) | Revision | Owner | Status |
|---|---|---|---|---|
CP-CTRL | _____ | _____ | _____ | open |
CP-NUM | _____ | _____ | _____ | open |
CP-PKT | _____ | _____ | _____ | open |
CP-CLOCK | _____ | _____ | _____ | open |
CP-BUF | _____ | _____ | _____ | open |
CP-LAT | _____ | _____ | _____ | open |
CP-FAIL | _____ | _____ | _____ | open |
CP-REL | _____ | _____ | _____ | open |
CP-PARAM | _____ | _____ | _____ | open |
CP-PROGRESS | _____ | _____ | _____ | open |
Status is one of open, pass, waived (with owner and expiry) or fail. The reviewer questions below test whether the evidence in each row is strong enough.
Reviewer question | Strong evidence |
|---|---|
Can data be lost? | Conservation scoreboard, boundary assertions, mutation result |
Can reset strand a transaction? | One-sided reset tests and recovery state diagram |
Does timing cover every clock? | Clock inventory, constraint audit, unconstrained-path zero |
What happens on UE? | Injected waveform, poison/stop behavior, CSR/IRQ record |
Can software recover? | Driver sequence for status, clear, abort, and restart |
Can the result be reproduced? | Locked manifest of sources, parameters, tools, libraries, and reports |
When residual work is bounded, owned, deadline-backed, and cannot invalidate already accepted evidence; otherwise the correct decision is reject.