WORKSPACE
Substrate signoff from geometry to evidence report
The primary buyer workflow chains TGV impedance, isolation, and yield screening into one design-to-yield call — with OOD state, solver-disagreement status, claim links, and pending external validation shown before report export.
A buyer verifies the compiled PDK with zero dependencies, and can make the verifier generate 26 forgeries of the object and reject every one …this result and the rest, each with its receipt Receipt for this result: pdk-portable-verifier.json (sha256 07ebcdf814bc…)
Every result has a receipt behind it
Each result this platform claims is quoted from its receipt in the public results record, with the command that reproduces it and a check that catches a planted defect. Open the Evidence Room and check one.
Open the Evidence RoomChecked against solvers we do not own
The sign-off geometries are re-solved by independent electromagnetic engines, FastCap and Palace among them. Where they disagree with ours, the disagreement is stated, not averaged away.
How cross-solver worksSimulation, said plainly
Everything here is computed. No fabricated wafer measurement stands behind any of it, and the pages that could imply otherwise say so.
How a release is validatedWorkflows
start anywhereGlass Package Signoff
Impedance + isolation + yield
Geometry + material + target → impedance, OOD, inverse alternatives, isolation, yield, solver disagreement, evidence report, next validation step.
PDK Playground
TGV + evidence trace
Explore substrate TGV impedance and inverse candidates, then escalate the design into the evidence-linked signoff workflow.
ChipletOS Photonic Signoff (alpha)
Photonic IC primitives
Sister sub-brand to the chiplet glass-TGV PDK. Waveguide + ring alpha run locally through a closed-form analytical model; a trained surrogate for it is on the roadmap.
Evidence Registry
Claim -> witness
Trace claim state, model cards, dataset provenance, witness JSON, and external validation blockers before using a result in a report.
Provenance Inspector
Audit-grade lineage
Paste any output and inspect the solver, dataset, validation, and pending-external chain behind each buyer-visible number.
EM Isolation
Isolation screening
Isolation and keepout screening with explicit caveats until external validation artifacts are attached to scoped claims.
Bondability
Yield screening
Bondability and yield-risk screening linked into the design-to-yield decision and evidence report.
Lot Intelligence
Process context
Lot-level process signals remain available as companion context, not the first buyer-signoff surface.
Wafer Explorer
Companion analytics
Wafer-pattern analytics stay disclosed as separate workflow support, not glass-package external validation.
Digital Twin Runner
Companion workflow
Multi-stage analysis stays behind the primary signoff workflow unless its outputs are linked to the current local evidence report.
Start here
Check us before you talk to us
The Evidence Room quotes every result this platform claims from its receipt in the public results record, with the command that reproduces it. It needs no account, and every receipt is a file you can download and hash yourself.
Open the Evidence RoomKeep agents downstream of the registry
The genesis-glass-pdk FastMCP package can drive local APIs, but buyer-facing answers must cite claim registry, witness, model-card, and data-catalog IDs.