Physical verification lab
Browser replay or visual evidence surface.
Open route ->DOMAIN LANE / EDA / LAYOUT
How do layout markers, connectivity reports, parasitics, and timing evidence become a public-safe verification claim?
ROUTE STACK
This lane collects the learning packets, replay labs, simulation objects, and evidence routes that belong together. It is a filter, not a new workflow engine.
Browser replay or visual evidence surface.
Open route ->Browser replay or visual evidence surface.
Open route ->Browser replay or visual evidence surface.
Open route ->Browser replay or visual evidence surface.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Supporting route.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->Concept sequence and review gate.
Open route ->Browser replay or visual evidence surface.
Open route ->Typed precomputed object with methods, limits, and exports.
Open route ->SIMULATION FILTER
Paper-writing users can enter from this page and open the relevant run cards, exports, methods, limits, and evidence without first watching a lecture.
Replay DRC and LVS issue classes as evidence cards with report confidence, triage priority, likely root cause, and safe next check.
Replay VDD, temperature, load, and path depth to connect Liberty-style delay terms with setup slack, hold slack, and timing-report criticality.
Filter tiny design, utilization, clock target, and buffering strategy to inspect WNS, congestion, route-risk, area, and power teaching proxies before a real reproducible flow.
Filter tiny RTL seeds, utilization, target clock, and routing effort to inspect WNS, TNS, congestion, marker-count, area, wirelength, and power proxy report fields before a real rights-cleared flow.
A browser CSV lab for reading DRC, LVS, PEX, and timing-handoff checkpoints as evidence, with public-safe SKY130 source anchors and no PDK collateral on the site.
A browser CSV lab that connects layout wire length, layer class, route style, load class, and checkpoint stage to RC, delay, slew, slack-risk, and evidence-state proxies.
A browser CSV lab for physical-design report literacy: compare utilization, aspect ratio, macro channel pressure, PDN strategy, clock topology, and report stage against placement overflow, RUDY-style congestion, global-route overflow, IR-drop risk, current-density risk, skew, insertion delay, timing-slack risk, and the next safe evidence check.
A browser CSV replay for reading standard-cell drive strength, input slew, output load, pin capacitance, area, setup/hold slack, and report-stage evidence without copying libraries or running EDA tools.
A browser replay that aligns clock-tree timing, route completion and RC, power-grid pressure, checkpoint maturity, owner view, and replacement evidence without running a live flow or implying signoff.
A browser replay that separates model assumptions, cell characterization, implementation evidence, test-structure intent, measurement availability, discrepancy review, provenance, uncertainty, and claim maturity without borrowing an external project's data.
DEEPENING PLAN
EDA and layout depth converts geometry into parasitics, constraints, violations, timing, and power integrity without redistributing restricted assets.
Build a layout evidence packet that turns one geometry choice into a quantified timing, noise, or rail consequence without publishing PDK material.
Open all-domain roadmap ->EVIDENCE BACKLOG
The backlog keeps future additions useful rather than noisy. New pages should enter through a domain tag, public source anchor, model boundary, and precomputed evidence package.
BOUNDARIES
Every domain can grow as education, simulation replay, and evidence planning. The page must not become a job board, tool controller, recipe workflow, upload service, or signoff surface.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
Keep this boundary attached when adding lessons, labs, simulations, resources, or research support.
SOURCE SPINE
These source links help name the domain. They do not convert teaching replays into certified measurements, process recipes, facility procedures, or product signoff results.
Open repository signal for DRC/LVS/PEX evidence literacy; no repository code or PDK collateral is mirrored.
Open source ->Open-source STA tool reference; this page does not execute OpenSTA.
Open source ->Public documentation context for timing-analysis flow vocabulary.
Open source ->Public tutorial context for setup/hold and report-reading language.
Open source ->Official flow-stage vocabulary; the public page does not run OpenROAD on the server.
Open source ->Open-source flow path reference for a future reproducible package; no third-party code is copied into this replay.
Open source ->Official ORFS repository anchoring RTL-to-GDS flow-stage vocabulary and public-flow boundaries.
Open source ->Official documentation anchoring configurable open digital-ASIC flow vocabulary.
Open source ->NEIGHBOR DOMAINS
Semiconductor work is coupled. These links keep the site navigable when one claim crosses process, device, circuit, memory, equipment, metrology, or reliability boundaries.
What changed on the wafer, and what evidence proves it?
Open domain ->How do charge, potential, materials, thermal path, and carriers become I-V, C-V, RF, or power-device evidence?
Open domain ->How does a device-level curve become gain, delay, and oscillation?
Open domain ->How does memory preserve, sense, move, disturb, retain, protect, and place data across SRAM, DRAM, HBM, NAND, MRAM, FeFET, SCM, CIM, and hybrid memory systems?
Open domain ->What cycle-level contract was actually checked?
Open domain ->What tool or facility condition supports the process, and what is still not an operating instruction?
Open domain ->Is the measurement fit for the claim?
Open domain ->What evidence remains after the die is fabricated, bonded, packaged, screened, and stressed?
Open domain ->