Drag the map or use pan buttons to move. Tab to a node or connection and press Enter to inspect its evidence. Arrows follow the actual claim direction.
CompanyChip / productTechnologyPlace / facility
Select a connection for its evidence
Relationships & evidence (6)
Every displayed connection is a scoped claim. Arrows follow subject to object.
The OpenROAD Project · Tier A · Primary source · supports
The ORFS flow diagram assigns GDSII generation and DRC/LVS checks to KLayout.
Location: Pinned README.md line 43: GDSII generation and layout checks
Published
Not stated
Retrieved
2026-10-13
Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.
Official openroad repository · Tier A · Primary source · supports
The OpenROAD README describes an ORFS flow whose synthesis stage uses Yosys. The OpenROAD application itself is not the complete ORFS flow.
Location: README / RTL-GDSII Using OpenROAD-flow-scripts
Published
Not stated
Retrieved
2026-10-13
Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms.
Official openroad repository · Tier A · Primary source · supports
The README names SKY130 among open PDKs supported in OpenROAD-flow-scripts; a selected platform and library configuration is required.
Location: README / PDK Support
Published
Not stated
Retrieved
2026-10-13
Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms.
ORFS documents OpenROAD use. Its README restricts guarantees to the latest matching OpenROAD/ORFS and warns that third-party versions are not guaranteed.
The OpenROAD Project · Tier A · Primary source · supports
The ORFS installation documentation identifies OpenROAD among its provided flow applications.
Location: Pinned README.md line 89: Physical implementation flow
Published
Not stated
Retrieved
2026-10-13
Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.
Official openroad repository · Tier A · Primary source · supports
The described ORFS finishing stage uses KLayout for GDSII output and DRC/LVS checks.
Location: README / ORFS Finishing
Published
Not stated
Retrieved
2026-10-13
Only original factual paraphrases, selected registry identity/revision/module metadata, source-byte hash and links are published. Complete source documents are not redistributed. Included code, libraries, PDKs and manufacturing use retain separate terms.
The OpenROAD Project · Tier A · Primary source · supports
The ORFS flow diagram assigns logic synthesis to Yosys.
Location: Pinned README.md line 19: RTL synthesis
Published
Not stated
Retrieved
2026-10-13
Store factual paraphrases, metadata, source-byte SHA-256 and pinned document link only. Source bytes were fetched for this review but are not retained or redistributed. Repository and component licenses remain separate. Commit date is not document publication or relationship validity.
From SKY130 Open PDK · up to two relationship steps.
A path retains its original claims. Shared technology does not establish a supply contract.
5 nodes · 6 claimsScope
Relationships may describe different dates. A path does not establish simultaneous activity. Bounded source-backed collection. Missing or filtered connections do not establish absence. Supported does not mean independently verified.
VLSI Korea