CDC Signoff Dashboard: Inputs & Outputs

Inputs and outputs contract

Inputs & Outputs for CDC Signoff Dashboard focuses on critical violations trend, closure burn-down, owner SLA adherence. 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 Signoff Dashboard

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

Key metric: critical violations trend, closure burn-down, owner SLA adherence

Ownership map

OWNERSHIP MAP — CDC Signoff Dashboard

artifact                  owner
----------------------    -------------------------
design intent           CDC lead
verification evidence   program management
signoff decision        design managers

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

CDC/RDC deep dive

Signoff is an evidence governance problem across teams.

Concept diagram

CDC SIGNOFF LOOP

analysis -> triage -> fix/waive -> review gate -> dashboard

Metric graph

CRITICAL OPEN COUNT

week1 34
week2 22
week3 10
week4 0

Reports and artifacts

• critical by owner

• waiver quality

• review gate status

• closure trend

Mini case study

Pass rates improved while critical waivers aged out of policy; dashboard exposed hidden risk.

Debug branches

• Separate quality from quantity metrics

• enforce waiver expiry

• run gate checklists consistently

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.

Principal CDC/RDC review addendum

Dashboarding translates thousands of crossings into actionable closure metrics by severity, block, owner, and risk state.

Metric: critical violations trend, closure burn-down, owner SLA adherence