Physical Design Domain Agent
The Physical Design Domain Agent focuses on implementation concerns such as placement, routing, timing closure, and signoff-oriented reasoning.
It is used when a workflow needs to translate design intent and synthesized results into layout-aware implementation decisions, physical tradeoff analysis, and signoff preparation.
What It Covers
The physical design agent helps with implementation-stage concerns, including:
- Converting requirements into floorplan and layout-oriented objectives.
- Guiding placement, routing, and implementation tradeoffs.
- Surfacing manufacturability, timing, and rules-driven risks earlier in the flow.
- Producing physical-design documentation and signoff-oriented collateral.
Task Capabilities
The physical design domain agent can rely on specialized task capabilities for layout and signoff-oriented workflows.
| Task Capability | Purpose |
|---|---|
| Requirement Coverage | Cover corner cases before floorplan creation begins. |
| Floorplanning | Perform autonomous placement coupled with ML-driven tools. |
| Routing | Apply specialized real-time DRC checking and intelligent wire optimization. |
| SDC Timing Predictor | Perform shift-left architecture analysis and timing tradeoff evaluation. Coming soon. |
| Rule Checker | Orchestrate DRC and LVS checking, plus GDSII generation. Coming soon. |
| AutoDoc | Generate comprehensive physical design and layout documentation. Coming soon. |
These capabilities allow the physical design agent to contribute both early implementation guidance and later-stage signoff support, depending on the maturity of the block or project.
Typical Use Cases
Use the physical design domain agent when you need help with:
- Preparing requirements and constraints before floorplanning starts.
- Evaluating placement and routing tradeoffs during implementation.
- Identifying physical-design risks earlier through timing- and rules-aware analysis.
- Coordinating signoff preparation steps such as checking and layout collateral generation.
- Producing documentation around floorplan, routing, and physical implementation intent.
Availability Notes
Some physical design capabilities are expected to mature incrementally as the broader implementation and signoff automation stack expands.
Capabilities marked as Coming soon should be treated as planned functionality rather than currently available standalone features.