Worked example

Worked Example for ML Timing & Power Prediction focuses on timing/power estimation error, scenario ranking fidelity, and iteration savings. The goal is to connect model behavior to hardware-aware decisions and operational risk.

A release check flags timing/power estimation error, scenario ranking fidelity, and iteration savings. Correct triage freezes revision tags, identifies failing layer, and validates one bounded fix before broad rollout.

System sketch under review

AI-VLSI FLOW — ML Timing & Power Prediction

problem framing
      |
      v
data + model definition
      |
      v
training / optimization
      |
      v
compute-hardware mapping
      |
      v
deployment + validation

Primary metric: timing/power estimation error, scenario ranking fidelity, and iteration savings

Surrogate prediction loop

SURROGATE LOOP

design features -> ML predictor -> estimated timing/power
                -> rank candidates -> full signoff on top-N

1. Capture failing workload and baseline comparator.

2. Record data/model/runtime/hardware revision tags.

3. Compare expected vs observed behavior on one focused slice.

4. Collect prediction-vs-signoff scatter plot, error report, and triage recommendation list.

5. Apply one reversible fix and define rollback before rollout.

Did the fix hold?

BEFORE / AFTER — ML Timing & Power Prediction

metric quality
  ^
  |                        o target region
  |                 o post-fix + regression
  |            o
  |      o baseline failing run
  +-----------------------------------------> iteration
      evidence audit   fix    full validation

AI-VLSI deep dive

EDA ML must prove signoff-correlated value with bounded risk and clear ownership.

Concept diagram

EDA ML GOVERNANCE

baseline flow -> ML assist -> confidence gate -> signoff confirmation

Metric graph

TRUST TREND

runtime gain            ███████
signoff correlation     ██████
false alarm rate        ███

Reports and artifacts

• correlation-to-signoff

• runtime savings dashboard

• false-prediction audit

• fallback decision log

Mini case study

A model improved placement runtime, but confidence gating avoided a high-cost false optimization suggestion.

Debug branches

• Tie model output to signoff artifact

• Audit confidence calibration

• Preserve deterministic fallback

Senior review question

Ask: what evidence connects this ML claim to a concrete VLSI workflow decision and owner signoff?

Key takeaways

• Every AI claim should map to a measurable engineering outcome.

• Validate both model quality and hardware/runtime feasibility before adoption.

Common pitfalls

• Optimizing benchmark metrics that do not correlate with signoff goals.

• Ignoring data drift and calibration after deployment.

• Shipping ML workflows without clear rollback ownership.

Execution drill pack 1

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 1

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 2

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 2

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 3

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 3

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 4

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 4

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 5

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 5

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 6

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 6

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 7

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 7

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 8

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 8

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 9

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 9

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 10

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 10

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 11

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 11

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 12

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 12

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Execution drill pack 13

Use this pack to rehearse AI-for-VLSI decision making on ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example: metric framing, mechanism proof, hardware implications, and release safety.

Evidence checklist

• Metric context includes workload, dataset slice, and revision tags.

• Mechanism explanation links model behavior to observed outcome.

• Hardware/runtime feasibility is profiled, not assumed.

• Owner and rollback path are documented before rollout.

Review prompts

1. Which decision will this model output influence?

2. What is the first failing layer when metric regresses?

3. Which owner applies the smallest reversible fix?

4. What validation matrix is required before deployment?

Evidence capsule

AI-VLSI EVIDENCE CAPSULE 13

PATH: ai-vlsi/ai-in-vlsi-workflows/ml-timing-power-prediction/worked-example
WORKLOAD SLICE: <name>
PRIMARY METRIC: <value/trend>
FIRST FAILING LAYER: <data/model/runtime/hardware>
OWNER: <name>
PRIMARY ARTIFACT: <report/profile/dashboard>
DECISION: <ship / rollback / escalate>

Principal AI-VLSI review addendum

Surrogate models approximate STA and power analyses to accelerate early exploration and prioritize full signoff runs.

Metric: timing/power estimation error, scenario ranking fidelity, and iteration savings