From architecture to tools
Once the project crosses into physical flow, every claim becomes more concrete. Tool adapters, environment setup, and wrapper behavior stop being implementation detail and become part of the product.
Back to atlas
Manufacturing
Physical path
Manufacturing Path
The platform is strongest when it shows the bridge between architectural ambition and actual physical flow constraints. The public site should explain that bridge directly.
Key points
Manufacturing is not just a future aspiration in this repo; it already changes how the code is organized.
The public story should show how physical-design constraints feed back into architecture and truth policy.
This also makes the project legible to foundry-facing partners.
EDA posture
OpenLane / OpenROAD
Physical flow is treated as a first-class stage.
PDK target
Sky130 path in repo
The project tracks real toolchain integration work.
Fab artifact
GDSII handoff
The pipeline is designed to end in manufacturable collateral.
What the repo is already doing
OpenLane bring-up notes, PDK setup scripts, and physical-mode gating are all present. That gives the public site enough material to explain the manufacturing route honestly.
Explicit environment variables for toolchain integration.
Docs for real-GDS execution and preflight.
Separate handling for synthetic and physical evidence.