You own Leakage vs Dynamic Tradeoffs on a block nearing implementation freeze — what do you verify first?
CLOSURE CHAIN
1. METRIC — name the failing report line (WNS, DRV, DRC count, IR %)
2. HYPOTHESIS — 2–3 likely causes ordered by probability
3. EXPERIMENT — one cheap check (corner, clock, report, map)
4. FIX — minimal physical or constraint change
5. REGRESSION — what you re-run and what must not regressTune VT mix, clock gating, and domain policies to hit power budgets without sacrificing closure or wake performance.
Section: Power Signoff
Primary artifact: power budget breakdown (leakage/dynamic by mode/domain)
Downstream dependency: next PD stage
Own Leakage vs Dynamic Tradeoffs as a release decision, not a page of notes. A senior PD engineer names the metric, the physical mechanism, the cross-team dependency, and the smallest evidence-producing experiment.
STAFF REVIEW MEMO — Power Signoff / Leakage vs Dynamic Tradeoffs
1. Current state
- Failing / watched metric: power budget breakdown (leakage/dynamic by mode/domain)
- Database tag, corner/mode, tool version: <fill before review>
- Physical scope: block, hierarchy, macro region, clock domain, or net class
2. Root-cause hypothesis
- Most likely mechanism: <name physical or constraint mechanism>
- Competing hypothesis: <name the second plausible cause>
- Evidence still missing: <report/map/schematic/check>
3. Proposed action
- Minimal reversible fix: <physical, constraint, ECO, or methodology change>
- Expected improvement: <metric delta>
- Regression risk: late-stage schedule slip, silicon risk, or cross-stage regression
4. Regression and signoff
- Re-run: power budget breakdown (leakage/dynamic by mode/domain)
- Must not regress: timing, routing, power, PV, DFT, package, or tapeout signoff
- Decision owner: PD ownermechanism — Mechanism
inputs-outputs — Inputs & Outputs
reports — Reports & Metrics
debug-playbook — Debug Playbook
worked-example — Worked Example
pitfalls — Pitfalls & Red Flags
interview — Interview Drills
checklist — Review Checklist
Master Leakage vs Dynamic Tradeoffs through reports, not GUI habit.
Power signoff validates whether the physical grid supports real activity.
static IR and dynamic IR maps with max drop percentage
EM ratio report by wire/via segment
activity source: vectorless, SAIF/VCD, or scenario-specific waveform
low-power cell placement: isolation, level shifter, retention, power switch
Dynamic IR fails near a clock-gated compute island during wake-up. Adding a far-away ring is not enough. Strengthen local straps/vias, add decap, and check wake sequencing.
If dynamic IR fails but static passes, correlate with switching vectors and clock domains.
If EM fails on vias, add via ladders or parallel straps rather than only widening wire.
If leakage fails, use HVT swaps on non-critical paths before reducing performance mode.
Ask yourself: what single report line would prove this page's concept is either passing or failing?
You are expected to predict what your fix can break before running it.
You should recognize when the issue is methodology, not one block's implementation.
You should communicate risk in tapeout language: owner, evidence, impact, mitigation, and decision date.
Lesson pages in this course should be read like real closure review material. For a 10+ year PD engineer, the bar is not remembering terminology; it is making a release-quality decision under ambiguity.
Names the failing metric, corner/mode, database tag, and analysis switches before proposing a fix.
Separates data, constraint, physical, tool, and methodology root causes instead of treating all failures as optimization problems.
Chooses experiments by information gain and reversibility, not by habit.
States regression blast radius across timing, route, power, PV, DFT, package, and tapeout manifest.
Turns recurring failures into methodology guardrails, dashboards, or checklist items.
STAFF / PRINCIPAL CLOSURE NOTE
Context:
stage: <pre-CTS | post-CTS | post-route | post-fill | signoff>
tag: <database / netlist / SDC / library stack>
failing metric: <exact report line>
affected scope: <block / hierarchy / path group / power domain / region>
Hypotheses:
H1: <most likely physical or constraint mechanism>
H2: <competing explanation>
H3: <methodology or input-data issue>
Decision:
next experiment: <cheap check that can falsify H1>
fix candidate: <minimal reversible change>
rollback trigger: <metric that says the fix is wrong>
regression set: <timing / route / power / PV / DFT / package>
escalation owner: <team or reviewer>Power signoff validates whether the physical grid supports real activity. Explain not only the preferred fix, but what margin or schedule you are spending to get it.
What must RTL, synthesis, CAD, STA, DFT, package, IP, or foundry agree to before this decision is final?
Which artifact becomes the source of truth after the decision: report, waiver, manifest, ECO script, or methodology deck?
What is the cost of being wrong: one rerun, ECO churn, mask risk, performance loss, or silicon escape?
"The current blocker is <metric> in <corner/mode/stage>. The leading cause is <mechanism>. I recommend <fix> because it is bounded and reversible. The regression surface is <domains>. If it fails, we escalate to <owner> with <evidence>."Always connect the concept back to a measurable signoff artifact.
A fix is not complete until you can name the regression checks.
Optimizing by habit instead of reading the current report.
Forgetting that a local fix can regress timing, routing, power, or PV elsewhere.