Skip to content

Packaging

Where an add-up-the-pairs baseline flips signoff verdicts, in simulation

116.07×the add-up-the-pairs shortcut’s worst signal error over our operator’s, on the worst layout a search found, against our own full-array solver

The result

What the add-up-the-pairs coupling shortcut costs at signoff: a searched worst case, a measured pass or fail flip rate, and a large field solved by declining to answer when unsure.

Limit Simulations against our own solver, not silicon; the worst case is one searched layout, and this record’s command re-checks one of three demonstrations.

Adding up coupling one pair of connections at a time is a simple shortcut, used here as our own baseline. In our simulations it does more than add error: it changes pass and fail verdicts. This page shows the worst case a search found, how often the shortcut flips a verdict against full-array truth, and a large connection field solved with no wrong verdicts, by declining to answer when unsure.

A dotted magenta underline marks a number read straight from a published file when this page was built.

On this page
  1. What it shows
  2. Why it matters
  3. Who should care
  4. The limits, in the record’s words

What it shows

The record states the result this way:

The published record says, word for word (an excerpt)

Three demonstrations turn the physics into signoff consequences: a searched worst case at 116.07×, a measured pass/fail flip rate up to 19.4%

In plain words: the figure above is the worst case a search of 1400 layouts found, where the shortcut’s error was that many times our operator’s, against our own full-array solver. Across 72 designs, the shortcut’s pass or fail verdict disagreed with full-array truth for 19.4% of them at the isolation spec where it did worst. The record’s third demonstration is a large synthetic field of connections solved with no wrong verdicts against our own solver, by declining to answer when unsure, and that costs escalations.

Why it matters

An extraction error matters most where it changes a verdict: a design that passes when it should fail, or one redesigned for nothing. Showing the flips, not just the error, is what makes the case.

What is ours, and what is not

Calibrated uncertainty and declining to answer are known methods (see the prior art below). What is ours is the operator that replaces the shortcut, the searched worst case, and the measured flip rates.

Who should care

  • Signoff teams who rely on pairwise coupling estimates for interconnect-dense packages.
  • Reviewers. The record’s partial coverage of its own reproduction is stated below.

The limits, in the record’s words

The published record says, word for word (an excerpt)

Signoff consequences against full-array BEM truth, not against silicon. Zero wrong signoffs is achieved BY ABSTENTION — 25–65% of cases escalate, which is the disclosed cost.

The published record says, word for word (an excerpt)

The 116.07× hero is at the CORRECTED provenance: the prior '110.7× CMA-ES hero' was a random_reference draw MISLABELLED as searched

The published record says, word for word (an excerpt)

The robust calibrated family figure is 37.4× [31.6, 45.5] over 42 geometries at conformal coverage 0.901. WallFinder's honest negative is surfaced: the BINDING worst-aggressor isolation error is sub-dB to a few dB, so the value is removing the over-design tax, not a dramatic headline. HBM4 shipped with its own honest negative — the random-layout conformal sidecar under-covers on a regular grid — which entry 13 (`conformal-risk-stack`)'s Gate 123 then fixed. PARTIAL COVERAGE (found 2026-08-27): this entry's reproduce command verifies the HBM4 demonstration ONLY - one of the three named in the claim. The 116.07x searched hero lives in benchmarks/wsx/manybody_failure_atlas_2026_06_27.json and the 19.4% signoff-flip rate in benchmarks/wsx/package_wallfinder_2026_06_27.json; neither is re-derived by the command above.

In plain words: these are simulations against our own full-array solver, not silicon. The worst case is a single searched layout, and the steadier family figure is lower. The command that reproduces this record re-checks only the third demonstration; the worst case and the flip rate rest on their own files, served here as extracts.

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.

Ask about a result, or check one yourself

Founder: Nick Harris. AI agents do our research and engineering. Each result page says how it was checked: against an outside solver, by an interval-arithmetic proof, by a Lean-checked step, or against our own simulator; these checks ran on our own machines. Who we are · How the work is checked

Every result on this site links to the file it comes from. Acquisition, licensing and partnership enquiries go to one address, nick@chipletos.com, and a person reads it.

Write to us Read the results

Each number links to the file it comes from; every file is listed, with its checksum, on Published files.

When a number is left off

We leave a number off a page, or mark it, when

  • its file has not loaded yet
  • nobody has looked into it yet
  • a search for it found nothing
  • its file holds no value for it
  • its file is missing or altered
  • files disagree on what it describes
  • its sample is too small for the claim
  • two files give different values
  • its file cannot be published
  • it was measured over ninety days ago
  • the question does not apply here
  • the program behind it stopped with an error