RDC Structural Checks: Reports & Metrics

Reports and metrics

Reports & Metrics for RDC Structural Checks focuses on unsafe reset crossing count, unresolved RDC warnings, waiver backlog. The goal is to convert issue observations into mechanism-backed closure decisions.

Reports must explain risk movement in unsafe reset crossing count, unresolved RDC warnings, waiver backlog, not just issue counts. A report is complete only when ownership and closure action are explicit.

Metric movement

METRIC TREND — unsafe reset crossing count, unresolved RDC warnings, waiver backlog

critical open issues
  ^
  |                target (0 critical)
  |              - - - - - - - - - -
  |          o post triage
  |      o initial run
  |   o baseline
  +--------------------------------------> review iteration

Always pair count trend with evidence quality trend.

Risk distribution

RISK HEATMAP — RDC Structural Checks

severity
high   |  XX  X
medium |  XXX XX
low    |  XXX XXX
        +----------------------------> ownership readiness
         unassigned   in-progress   closed

Metric focus: unsafe reset crossing count, unresolved RDC warnings, waiver backlog

• Track unsafe reset crossing count, unresolved RDC warnings, waiver backlog by block, mode, and severity.

• Separate structural warnings from behavior-proven hazards.

• Show waiver age and owner SLA alongside raw counts.

• Store evidence links with each closure claim.

CDC/RDC deep dive

Reset release ordering is a first-order reliability contract.

Concept diagram

RESET RELEASE FLOW

assert global -> clocks stable -> sync release per domain -> first transaction

Metric graph

BOOT STABILITY

passes per 1k boots: 920 -> 980 -> 999

Reports and artifacts

• reset dependency matrix

• RDC warning classes

• boot stress logs

• waiver aging

Mini case study

Domain B released before producer A was valid, causing rare startup deadlock.

Debug branches

• Correlate reset and clock timelines

• verify async assert/sync release

• exercise skewed release tests

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.

Reading evidence