eda-preflight-reflect

To validate route and timing evidence before EDA experiments, analyze case-level TSV/MD summaries, routed DEF occupancy, reroute reports, and timing delta metrics to produce a go/no-go decision with explicit acceptance criteria.

A preflight check in EDA routing and STA workflows is a disciplined review of route geometry, reroute reports, and timing deltas that ensures experiments start from verifiable evidence rather than policy-driven artifacts lacking geometric backing.

Identify method gaps in EDA reroute planning by applying a structured reflection checklist evaluating backside presence, long-net capture, timing consistency, capacity pressure, and policy-vs-model dominance to generate a pass/fail output.

Yes, you can generate ranked root-cause hypotheses from timing delta metrics and reroute reports by collecting case-level artifacts and producing one-line hypotheses with minimal A/B/C next-step plans and acceptance criteria.

Run a preflight reflection on EDA routing experiments before submitting new reroute experiment batches to avoid resubmitting policy-driven artifacts that lack geometric backing or that worsen timing outcomes.

Acceptance criteria for STA preflight checks should include timing consistency validation, capacity pressure evaluation, and explicit pass/fail thresholds for policy-vs-model dominance before producing a go/no-go experiment submission decision.