CDC/RDC Whiteboard Framework: Inputs & Outputs

Inputs and outputs contract

Inputs & Outputs for CDC/RDC Whiteboard Framework focuses on problem decomposition quality, mechanism-first answer quality. 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.

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

CROSSING FLOW — CDC/RDC Whiteboard Framework

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

Key metric: problem decomposition quality, mechanism-first answer quality

Ownership map

OWNERSHIP MAP — CDC/RDC Whiteboard Framework

artifact                  owner
----------------------    -------------------------
design intent           candidate
verification evidence   interviewer
signoff decision        hiring panel

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

CDC/RDC deep dive

Interview performance reflects production signoff thinking quality.

Concept diagram

INTERVIEW FLOW

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

Metric graph

PRACTICE SCORE

session1 62%
session2 78%
session3 89%

Reports and artifacts

• scenario completion

• answer rubric scores

• trap recovery quality

Mini case study

Candidate gave command-heavy answer but missed risk framing and waiver governance.

Debug branches

• Use mechanism-first structure

• name ownership and evidence

• close with signoff decision

Senior review question

Ask: what evidence proves this risk is closed for silicon, not just tool-clean?

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.