lumiculelight does the math

The workbench

One flow, from cell to packaged chip

The workbench holds the whole design: a per-domain workspace, a solver cockpit, and an evidence trail recording what produced what. Pick a stage, run it, decide from the results.

Platform flow

The stages, and what runs at each one

Every stage is a recorded job, not a script you hope behaves. Pick one.

Cells & PDK

Cells arrive from the process design kit with geometry, cross-sections, ports and measured S-parameters. Placing a cell puts real process geometry on the canvas, not a placeholder.

Platform capability: PDK component catalogue

Candidate compare

Choosing, with the evidence in front of you

Every stage ends in a decision. Candidates are compared against the target, and the one that is picked carries its evidence.

Candidate compare — illustration, fixed sample data

Target

Platform

Band

Ring crossbar 8×8 — balancedselectedpasses 7 of 7 checksGDS · S-params · BOM
Ring crossbar 8×8 — low-losspasses 6 of 7 checksGDS · S-params · BOM
MZI mesh 8×8 — compactpasses 5 of 7 checksGDS · S-params · BOM

Illustration with sample data — no design is running here. Open the platform to generate real candidates, and to see which checks each one passes.

The tile

Five domains, one package

A cross-section of the co-packaged optics tile: carrier PCB, EIC driver die, flip-chip bumps, PIC ring crossbar, and lensed fiber array — designed together in one browser workspace.

Cross-section of the co-packaged optics tile: carrier PCB at the bottom, EIC driver die with 4096 DAC channels, flip-chip bumps and underfill, PIC die with 64x64 ring crossbar, and a lensed fiber array on top, with an optical ray path and a top-down inset of the ring array.

Publication-quality vector figure generated with the schematic-figure skill (MIT, lgwrightlab). Full design process: figure/docs/brief.md, spec.md, facts.md, concepts.md.

From spec to signoff

Verified outputs, not just simulations

A layout that simulates is not a layout that can be built. Every stage has to survive a check that is capable of failing it.

Physical

DRC and LVS
Design-rule checking against the process kit's rules, an independent second engine cross-checking it, and layout-versus-schematic to confirm the layout is still your circuit.

Logical

Formal, not just simulation
RTL is compiled, simulated, formally proved and synthesised. Temporal proofs cover safety and liveness, and every proof is gated for vacuity — a pass means the property was reachable.

Analogue & optical

SPICE and photonic solvers
Analogue cells run in SPICE, including a derivative check between AC and DC — the bug class that hides from a transient-only run. Optical structures run in the EM solvers.

Three outcomes, not two. A verification run ends CLEAR when every applicable mode was verified, NEEDS GUARDS when there are silent gaps, and BASELINE FAILED when the design does not even simulate. Reporting the gaps is the point.

AI proposes. Deterministic engines dispose. Designers decide. The platform is built so that the last of those three is always a person. Meet the agents →

Where the cost actually is

Finding out why it failed

“Does it pass?” is the easy half. Wilson Research puts debugging at 44–47% of project time, so we ship the toolchain that ends in a cause, not a guess.

01 · Fault injection

Break it on purpose, then look
A guard-band suite injects six fault modes across three families — reset, handshake, datapath — runs each against a baseline, and reports per-mode evidence: assertion hits, a baseline differential, and the waveform. The verdict is one of three: CLEAR, NEEDS GUARDS, or BASELINE FAILED.

02 · Learned diagnosis

A family, not a log
Each failing run becomes an eleven-dimensional feature vector. A trained classifier predicts the fault family and reports its per-family true-positive rate, so a failure arrives classified instead of as another thousand lines to read.

03 · Waveform evidence

Localise from the trace
Five query classes over the failing VCD: browse a signal through its hierarchy, find where two runs diverge, scan a driver for its source, follow the active path, lift packed values into their state. The narrowing loop returns a candidate mechanism with its evidence — and the ambiguities it could not resolve.

04 · Formal anchor

A failure you can replay
A failure is recorded as F = (S, V, R) — preconditions and trigger, the behaviour that was violated, and a reproduction recipe. The anchor is validated by replaying it, so it is a reproducible artefact rather than a description of something that once happened.

05 · Propagation scope

Which sites a fix has to touch
An elaboration-aware repository relation graph locates repair sites at declaration, implementation, structural-binding and generated-RTL level, then narrows to the set a change must reach — so a coordinated fix is a list, not a search.
All of it hangs off the same gate list. The toolchain is wired into the ten-gate signoff pipeline with auto-feedback, so a failed gate does not just stop the run — it hands back the next action. And a checker is only believed once it has been shown capable of failing: the clearance checks ship with a deliberately-colliding negative control that must fail, and formal proofs are gated for vacuity, so a green result can never come from a checker that looked away.

What is measured, and what is quoted. The fault-injection suite, the diagnosis classifier, the waveform queries, the formal anchors, the relation graph and the gate list are all in the platform and run today. The 44–47% figure is third-party — Wilson Research, cited in our own reference notes via artl.ai — not a measurement of ours.

Reliability & qualification

JESD264, clause by clause

JEDEC's silicon-photonics qualification framework is executable here: every clause mapped to its test conditions, sample sizes, intervals and pass-fail criteria, then reported clause by clause.

Every clause, what it covers and what it applies to24 clauses
The JESD264 clause catalogue
ClauseWhat it coversApplies to
4.2Reliability and service-life requirementsAll SiPh products
4.3Standard production screeningQualification dies and sub-components
4.4Sample selection and test vehicleAll qualification samples
4.6Measurement intervalsAll stress-based tests
4.7ESD characterizationBare dies and integrated chipset assemblies
5.1Generic micro-optic devices — the base stress matrixModulators, PDs, waveguides, thermal resistors
5.2Photodiode qualification — dark current, responsivity, SOA, TDDB, high optical power, HCIPhotodiodes
5.3Electro-optic modulator qualificationPN, PiN, SISCAP, EAM
5.4Thermo-optic phase-shifter qualificationTOPS, resistor element in BEOL
5.5Thermal resistor qualificationFEOL silicon
5.6Decoupling capacitor qualificationFEOL polysilicon or SiOx
5.7Waveguides and passive opticsSplitters, couplers, PSR, MUX/DMUX, VOA, crossings
6Bare die — no optical or active devices attachedSiPh die
7Integrated chipset, with or without flip-chip attached die1D–3D integration
8.1Die pad wirebonding — pull and ball shearDRIE cavities / UBM processed outside the foundry
8.2Component shearDirectly attached die, chips and optical sub-devices
9BEOL reliability — Al, Cu, W, contacts, vias, MIMCAP, resistorsBack-end structures
10TSV / chip-on-chip / chip-on-chip-on-substrate stack-upAll 2.5D and 3D stacking
11.1Laser on submount, and butt-coupled lasersFabricated lasers adjacent to the die
11.2Fabricated laser attached to the SiPh dieSolder, metal or polymer bond
11.3Laser chiplet bonded to the die surface, and micro-transfer printingIII-V, TFLN and LN coupons
11.4III-V laser grown epitaxially in the SiPh waferUnder investigation, not commercialised
12Optical I/O — fibre array unit attachEdge, vertical and evanescent coupling
13Manufacturing process, QC, yield, data, traceability and ORTWafer fab and assembly

Clause 11 matters most for photonics: laser integration is four distinct qualification problems, because a laser on a submount, bonded to the die, micro-transfer-printed and epitaxially grown do not fail the same way.

Twenty-four clauses, eighty-two protocols. The six that stress a part and measure it are executable, not prose: each computes its own pass or fail against the standard's end-of-life criteria and extrapolates a lifetime.

Clause 5.1

Optical burn-in
Measures optical parameters before, during and after stress — insertion-loss drift, wavelength shift, coupling degradation, photodiode dark current and responsivity — not just whether the part still works.

Clause 5.2

Photodiode stress
Four protocols: safe-operating-area mapping, wear-out, high optical power at least 3 dB above normal operation, and hot-carrier injection for gain photodiodes — each extrapolating a lifetime.

Clause 9

BEOL reliability
Electro-migration by Black's equation, stress-migration resistance change, deep temperature cycling from −65 °C to 150 °C over 500 cycles, and dielectric integrity under constant and ramped voltage.

Clause 8.1

Wirebond qualification
Initial pull and ball shear to JESD22 methods, then temperature cycling, unbiased damp heat and high-temperature storage with pull and shear measured at intervals.

Clause 11

Laser burn-in
A burn-in development matrix over temperature, bias and duration; accelerated aging for the equivalent of one to two years of operation; and the shift limits the part must hold.

Clause 12

Fibre array attach
Shear and pull to MIL-STD-883, temperature cycling with optical power injected, damp heat, high-temperature storage, 500 G shock, and 20 G vibration from 20 to 2000 Hz.
What this is, and what it is not. It is a protocol generator and a compliance reporter: it produces the test conditions, sample plan and criteria, and reports a project against them clause by clause. JESD264 does not replace the JESD22 stress methods it builds on — the standard says so, and so do we. Nothing here is described as qualified: a part is qualified when it has been through the plan, and not before.

Depth

Three things most flows do not do

Each of these is a place where the industry settles for an estimate. We measured instead, and the measurement is what the claim rests on.

Packaging geometry

Clearances measured, not stacked
Most packaging reviews add up nominal dimensions and hope. This one measures: real solid geometry answers whether a module fits, as an interference volume in mm³ with an explicit keep-out limit — so “it fits” is a number, not an opinion.
How the check is built3 questions, 2 controls

Does the fibre array clear the lid and cold plate? Does the bond loop fit under the lid cavity? Does the bump field stay inside the die footprint?

It runs on an open-source NURBS kernel rather than a commercial CAD kernel, so no Parasolid-class licence stands between a customer and packaging verification. Geometry exports as USD for review and meshing.

The check is built to be falsifiable: every clearance check ships with a negative control — a deliberately-colliding case that must fail, so a green result can never come from a checker that looked away. On our reference cases the closed-form and kernel paths agree to within 2×10⁻⁶ %, and both negative controls fire.

Sourcing

Second-source-ready parts
Parts are grouped by footprint and pinout across manufacturers, so an equivalent part from a second source drops into the same board without a re-spin. Design-assist checks flag the requirements that conflict before layout rather than after it — which is the difference between a sourcing decision and an engineering change.

Analogue

Validation beyond DC
A device model can have derivatives that are wrong in the small-signal path while every DC sweep looks perfect — the failure mode is invisible to a transient-only check and wrong the moment an AC or noise analysis runs. So the numerical derivative from a DC sweep is compared against the small-signal derivative from an AC analysis at the same operating point, across frequency, and the noise path is validated end-to-end against an exact bench. A model error cannot hide below a solver tolerance.

Where these stand. All three are implemented and measured on our own reference cases, which is what the figures above report. They are not claims about every process or every design — a clearance check is only as good as the solids it is given, and the derivative check only as good as the deck it reads.

Proof

What we have actually done

Not a roadmap. Each row is something that exists, and where the platform has a number for it, the number is here.

What we have done, and what it means
What we have doneWhat it means
Design-rule clean chip layoutsOur designs pass foundry signoff checks and are ready for fabrication
Photonic compute precision on real models27.4 dB signal-to-noise on GPT-2 Small and 27.5 dB on GPT-2 Medium, at full precision
SPICE-verified analogue cellsCircuit performance confirmed in simulation before anything is fabricated
Full-stack chip integrationPhotonic, electronic, firmware and packaging designed together in one platform
Calibrated on measured dataModels trained on measurements from real components, not only on simulation
Machine-checked temporal proofsControl RTL proven for safety and liveness — with reachability covers, so no proof passes vacuously
Second-source-ready partsComponent groups verified for footprint and pinout compatibility across manufacturers
Packaging clearances measured, not assumedSolid geometry returns interference volumes with keep-out limits, and the closed-form and kernel paths agree to within 2×10⁻⁶ %
Analogue validated beyond DCDevice behaviour confirmed across simulation formulations, plus noise-path validation
A live design platformA working web IDE with agents, design tools and verification, reachable from anywhere
5 → 1
PIC, EIC, FPGA, PCB and Chiplet in one project tree
6
PDKs with an explicit DRC support status — including the limited ones
3
Measurement platforms feeding the model calibration
0
Signoffs taken on an AI's word alone

Read this before you commit a run

Know the limits first

Support differs by process. This is the honest picture of our DRC signoff path per PDK, taken from our own support matrix.

DRC signoff support by PDK
PlatformTypeDRC path in the IDEStatus
IHP SG13G2SiGe BiCMOSLayout-native checker + independent second engineFull
SG13CMOS5LCMOSLayout-native checker + second engineNear-full
GF180MCU-DCMOS 180 nmLayout-native checker + second engineNear-full
GF180MCU-ACMOS 180 nmIndependent second engine onlyDRC-only
IC Sprout 55CMOS 55 nmIndependent second engine onlyDRC-only
SKY130ACMOS 130 nmLayout import pathLayout import
CORNERSTONE SOISilicon photonicsPhotonic cells, DRC and EM solversPhotonic flow

What the statuses mean. Full — both the layout-native checker and the independent second engine are available. Near-full — both run, with known rule-coverage gaps we can name. DRC-only — only the independent engine is wired up, so we do not claim parity with the layout-native path. Layout import — layouts can be read and edited, but treat DRC as your responsibility in that process. Ask us for the current matrix before you plan a tapeout.

Devices & foundries

What you can design today

Photonic and electronic design in one catalogue — cells, waveguides, splitters, couplers, crossings, modulators, detectors, heaters, pads, die templates — each with the ports, cross-sections and measured S-parameters it needs to be simulated.

Passive photonics
Waveguides, bends, splitters, couplers, crossings, tapers, grating couplers, MZIs, ring resonators.
Active photonics
Modulators, detectors, phase shifters and heaters, with the drive and bias considerations that come with them.
Electronics
Driver and analogue cells, standard cells and device models, verified in SPICE and by formal methods. Through the open-source virtuoso-bridge (run on your Virtuoso host, where the licenses live), agents can drive Cadence Virtuoso and Spectre for analog/mixed-signal work — SKILL automation, netlist simulation, license checks — behind the same deterministic verification gates.
Assembly
Die templates, pads, interposers, boundary manifests and package-level checks — thermal, mechanical and power.
Measurement and design platforms quoted in the platform
PlatformMaterial systemUsed for
SOI 220 nmSilicon-on-insulatorWaveguides, rings, MZIs, grating couplers
SOI 340 nmSilicon-on-insulatorWaveguides, rings, MZIs
SiN 300 nmSilicon nitrideLow-loss passives, visible / near-IR

Component counts, layer maps and port lists are read live from the platform catalogue, so they change as PDKs are imported. Ask for the current numbers rather than quoting these names as a fixed list.

IP, exports & deployment

Your designs never stop being yours

Built for teams whose layouts cannot leave their control: you own what you make, you can verify it independently, and you decide where it runs.

You own the IP
Circuits, layouts, RTL, board and package all belong to you. Nothing about the platform makes your design dependent on continuing to pay us.
Portable, verifiable exports
GDS, Touchstone S-parameters, RTL, netlists and a BOM — standard formats, so you can re-simulate our work in the solver you already trust.
Your data, your infrastructure
Every run is recorded with its tool, inputs and status, and the platform can run where your data has to stay.

Where the work runs

Cloud
Managed for you. Sign in from a browser: compute, updates and scaling are ours, and the heavy solvers run on our EDA infrastructure rather than your laptop.
On-premise or your own cloud
For designs that cannot leave your network, including air-gapped environments. Your projects, artifacts and measurements stay on infrastructure you control.
Signed, fail-closed installations
Whichever way it runs, what ships is auditable: no credentials are ever baked into the software, execution services refuse to run unconfigured, and every installation carries a signed provenance seal your security team can check from a single health call — without giving us access to your site.

Deployment options are engagements, not a button on a pricing page. Tell us the constraint — data residency, air-gap, procurement — and we will tell you honestly whether we can meet it today.

Don't take our word for it

Verify our work yourself

Every design leaves in formats your bench already reads. Re-run the simulation and compare — if they disagree, that is a bug we want to hear about.