Pillar C · State as of 2026-09-10

Who submits the classical rival on the Quantum Advantage Tracker?

As of 10 September 2026, 12 instances on the tracker have both a quantum arm and a classical challenger. In 8 of them every classical rival shares an institution with the quantum team — and all five instances of the observable-estimations registry are in that group, while all three classically-verifiable instances are contested by outsiders.
→ Leer en español
State as of: 2026-09-10

The Quantum Advantage Tracker, launched by IBM and Algorithmiq in November 2025, does something the field badly needed: it puts quantum results and classical rivals on the same instance, with circuits and data attached, where anyone can look. We use it. This note is about one thing we found while looking, and it is not a criticism of the tracker — it is a measurement of who is showing up.

On 10 September 2026 we downloaded the three submissions.json files from the tracker's own repository and counted. Not the homepage summary: the data.

What we counted

Forty-seven entries across the three registries. Seventeen of them are quantum runs; the rest are classical methods submitted as rivals or baselines. Twelve instances have both a quantum arm and at least one classical challenger — those are the only ones where a comparison exists at all.

In 8 of those 12, every classical rival shares a submitting institution with the team that ran the quantum experiment.

The concentration is not spread evenly, and where it clusters is the interesting part:

RegistryInstances with both armsOnly same institutionsWith an outside challenger
Observable estimations550
Variational problems431
Classically verifiable problems303

Observable estimations is the registry where expectation values arrive with error bars — the format in which advantage gets announced. No third party has ever submitted a classical method there. Classically verifiable problems is where the answer can be checked from outside without anyone's permission. Every instance there is contested by an outsider.

Outside scrutiny appears where a result can be verified without permission, and disappears where you have to trust the party doing the measuring.

The clearest case

The tracker publishes institutions for all 47 entries and author names for 16. On the instance guided_sparse_ground_state_problem_49Q_v1 the names are enough to settle it: the quantum entry (SKQD, from IBM, RIKEN and the University of Chicago) and all five classical rivals — DMRG, Truncated Arnoldi, ASCI, CIPSI and HCI — carry the identical author list, person by person. It is not shared employers. It is one team competing against itself, six times.

Four cases that cut the other way

We are naming these because the finding is weaker without them, and because a claim that only survives when you omit the counter-examples is not a finding.

What this is not

It is not evidence that anyone shaped a result. Submitting the strongest classical rival to your own quantum claim is the honest thing to do, and several groups here did exactly that — including against themselves. The measurement is about who else showed up, and the answer for the loudest registry is: nobody, yet.

It is also not the same question as reproduction. Across all 47 entries there is no instance where two quantum arms come from disjoint groups — that is, nobody has re-run another team's quantum experiment and confirmed its headline result. Refuting a claim, verifying an output and competing against it with a classical method are three different acts, and all three have happened. Reproduction has not.

The distinction matters in a case that is often cited as if it settled the question: in the doped Clifford episode, a team at the Singapore University of Technology and Design computed the exact amplitudes of the 2,051 outputs IBM had published. That is independent verification of the output, and it is real. It is not reproduction of the experiment, and it is not confirmation of the advantage — what narrowed was the time gap, while the certificate held.

Check it yourself

Everything above comes from three files. Download data/observable-estimations/submissions.json, data/classically-verifiable-problems/submissions.json and data/variational-problems/submissions.json from the tracker's repository, group the entries by circuit or hamiltonian, and compare the institutions field of each classical entry against the quantum one on the same instance. It takes about twenty lines of code. If your count differs from ours, we want to know.

We will re-run this on the next edition. The number worth watching is not 8 of 12 — it is whether the first outside classical submission ever lands in observable estimations.

Sources:
· Quantum Advantage Tracker — submissions.json (3 registros)
· Quantum Advantage Tracker

Get the next one.

One email a week: what the evidence engine published and what moved in the registry. No pitches.