What it shows
The record states the result this way:
The published record says, word for word (an excerpt)
Before an optimizer promises a geometry, the requested impedance target is proved reachable and the manufacturable geometry is returned as a certified interval, or refused.
In plain words: because the stand-in’s impedance is proved to move in one direction as the via pitch changes, each target has at most one matching pitch, and a bisection that keeps every step’s error bounded finds it as an interval. In the record’s run, every one of 143 targets was certified, and all 143 soundness checks passed.
Why it matters
A promise of a geometry that cannot meet its target wastes a design iteration, or worse, a build. A proved yes or a proved no before the optimizer runs removes targets the stand-in itself cannot meet; a physical build can still miss.
What is ours, and what is not
Proving monotonicity of a network and enclosing a root by interval bisection are known (see the prior art below). What is ours is their use together on our impedance stand-in over a manufacturable range.
Who should care
- Package designers who set impedance targets and need to know early whether a geometry can meet them.
- Reviewers. The certificate is about the stand-in, and the page says so.
The limits, in the record’s words
The published record says, word for word (an excerpt)
Certifies a property of the SURROGATE FUNCTION over the admitted parameter box, not physical reachability. It does not establish yield, manufacturability, or measured-hardware performance.
In plain words: this proves something about the stand-in model over its allowed range of inputs. It does not establish yield, manufacturability or how a built package performs.
Open source for this step
Tools and datasets we publish for the package step of building a multi-chip package. They are the checkers around this work, not a copy of the result itself.
- physics-lint: One command that checks a folder of physics models against a fixed set of named physical rules, with findings straight into CI.
- maxwell-lint: Flags a coupling extractor whose answers no passive set of conductors could produce.
- sparam-lint: Is your signal-response model physically possible? Five physical laws checked from the command line.
- interval-core: The interval arithmetic core behind our proofs over whole families of layouts.
- touchstone-tools: Read, write and convert Touchstone files, the standard text files that record how signals pass through a package's connections, and refuse to write one that cannot be read back.
- physics-lint-mcp: The physics checks, callable by an AI agent.
- physics-lint-action: A GitHub Action that fails the build when a model breaks one of a fixed set of named physical rules.
- Signal-response validity corpus: A labelled corpus of physically invalid signal-response networks, and a scorer that grades any checker against it.
- screening-ceiling: The screening-ceiling family as an open dataset.