Debug playbook

Debug Playbook for Abstract Models (LEF/DEF/Timing) focuses on abstract-model mismatch defects, floorplan integration churn. The goal is to map symptoms to boundary contracts, owner actions, and regression-proof closure.

Integration debug is a search for the first contract break, not the loudest downstream failure signature.

Root-cause tree

ROOT-CAUSE TREE — Abstract Models (LEF/DEF/Timing)

abstract-model mismatch defects, floorplan integration churn regressed
         |
   same baseline manifest?
      /           \
    no             yes
    |               |
version/collateral  real integration
mismatch            contract break
 /       \            |
inputs    env      isolate domain
drift     drift    and first failure

1. Freeze baseline manifest and owner matrix.

2. Find first failing boundary and earliest reproducible symptom.

3. Classify failure type: contract, collateral, implementation, or governance.

4. Prove with one reduced experiment.

5. Apply smallest owner-controlled fix.

6. Run focused verification and full cross-domain regression.

Review memo template

STAFF SOC REVIEW MEMO — IP Integration & Handoff / Abstract Models (LEF/DEF/Timing)

1. Symptom
   - Watched metric: abstract-model mismatch defects, floorplan integration churn
   - Failing integration boundary: <domain/interface>
   - Baseline manifest: <hash/tag>
   - Repro setup: <sim/emulation/fpga/silicon + fw tag>

2. Mechanism hypothesis
   - Primary mechanism: Top-level integration relies on abstract views (timing, physical, power) that must remain aligned with evolving implementation details.
   - Competing hypothesis: <contract drift, collateral mismatch, implementation bug, governance gap>
   - Missing evidence: <trace, report, checklist, signoff artifact>

3. Proposed action
   - Minimal reversible fix: <contract update, config patch, RTL fix, process guardrail>
   - Expected metric movement: <delta and scope>
   - Regression risk: timing, power, functionality, schedule

4. Signoff
   - Re-run artifact: abstract model manifest, LEF/DEF consistency report, timing-model diff
   - Required owners: PD owner, IP physical owner, STA owner
   - Final decision: close, waive (bounded), or escalate

SoC deep dive

IP handoff quality and version governance drive integration velocity.

Concept diagram

IP HANDOFF PIPELINE
IP package -> baseline lock -> integration build -> bring-up

Metric graph

INTEGRATION CHURN
collateral gaps ██████
version drift █████
real logic bugs ███

Reports and artifacts

• handoff completeness score

• manifest diff report

• model mismatch log

• bring-up issue tracker

Mini case study

Most top-level debug time was spent on collateral drift, not RTL defects.

Debug branches

• Validate handoff checklist

• Lock manifest hashes

• Correlate issue to owner boundary

Senior review question

Ask: what baseline, owner, and artifact prove this topic is truly closed?

Key takeaways

• State baseline manifest and owner with every closure metric.

• Run cross-domain regression after every top-level fix.

Common pitfalls

• Comparing results across different manifests.

• Unowned issues slipping through review cycles.

• Waiving risks without expiry and validation plan.

Principal SoC review addendum

Top-level integration relies on abstract views (timing, physical, power) that must remain aligned with evolving implementation details.

Metric: abstract-model mismatch defects, floorplan integration churn