CDC / RDC · All levels

Scenario: Waiver Debate: Inputs & Outputs

Inputs & Outputs for Scenario: Waiver Debate.

Inputs and outputs contract

Inputs & Outputs for Scenario: Waiver Debate focuses on risk framing quality, waiver justification quality, escalation judgment. The goal is to convert issue observations into mechanism-backed closure decisions.

Treat CDC/RDC signoff as a contract across architecture, RTL, DV, and signoff governance. Most late surprises are contract mismatches, not tooling gaps.

diagram

INPUTS
  - crossing inventory with intent classification
  - reset tree and release dependency model
  - protocol assumptions and assertion package
  - CDC/RDC tool configuration + waiver policy

OUTPUTS
  - severity-tagged open issue list
  - protocol/reset proof evidence
  - owner-assigned closure plan
  - signoff or escalation memo

Crossing sequence

diagram

CROSSING FLOW — Scenario: Waiver Debate

source clock domain -> launch signal -> crossing structure -> destination sample
      |                    |                 |                    |
   source FF           protocol           sync / fifo         destination FF

Key metric: risk framing quality, waiver justification quality, escalation judgment

Ownership map

diagram

OWNERSHIP MAP — Scenario: Waiver Debate

artifact                  owner
----------------------    -------------------------
design intent           candidate
verification evidence   signoff lead
signoff decision        program lead

Every open CDC/RDC issue needs one accountable owner before waiver or fix.

Scenario debrief

Score each response on mechanism clarity, evidence quality, and signoff decision discipline.

diagram

INTERVIEW FLOW

classify -> explain mechanism -> propose fix -> state regression

diagram

PRACTICE SCORE

session1 62%
session2 78%
session3 89%

Debrief prompts

Which crossing class or reset dependency failed first?
What evidence changed your decision?
Fix, waive, or escalate and why?

Key takeaways

State crossing class, assumptions, and owner with every issue.
Run structural and dynamic regressions after each fix.

Common pitfalls

Treating all warnings as equivalent risk.
Waiving issues without containment evidence.
Skipping reset and reconvergence stress after CDC fixes.

Practice this lesson