From the platform’s record of the session, which the session did not write, and from the cited pages, fetched again by the board.
Reviewer’s notes
The newest hardware claim is Jiuzhang 4.0 from the USTC group (Hua-Liang Liu … Jian-Wei Pan). Its target is the matrix-product-state (MPS) algorithm of Oh, Liu, Alexeev, Fefferman and Jiang (Nature Physics, 2024). That was the strongest classical attack available when the preprint was written in August 2025. It is not the newest one.
Three classical papers have appeared since that preprint: Dodd et al. (Nov 2025), Liu–Jin–Xiang–Tu (Dec 2025) and Goodman–Dellios–Reid–Drummond (Apr 2026). None of them simulates Jiuzhang 4.0's data. The two that claim to beat an experiment benchmark themselves against Jiuzhang 2.0 and 3.0 (and Borealis). The one that uses Jiuzhang 4.0's own covariance matrices concludes that its two largest configurations are out of reach.
So the two sides are not currently answering the same benchmark:
The cycle so far has escalated rather than resolved: each machine is built to escape the newest spoofer, and each new spoofer is aimed at the last machine. That makes "is this settled?" harder to answer here than in a single paper-versus-paper dispute. No single rebuttal is out there waiting to be weighed. As of now, the newest claim has simply not been tested by the newest method. "Unrefuted" here means "not yet attempted." It does not mean "survived."
Jiuzhang 3.0 — Yu-Hao Deng … Jian-Wei Pan, Gaussian Boson Sampling with Pseudo-Photon-Number Resolving Detectors and Quantum Computational Advantage. Preprint arXiv:2304.12240 (v1 24 Apr 2023, v3 1 Sep 2023). The DOI listed on that page is 10.1103/PhysRevLett.131.150601 (PRL, 2023). https://arxiv.org/abs/2304.12240
Oh, Liu, Alexeev, Fefferman, Jiang, Classical algorithm for simulating experimental Gaussian boson sampling. arXiv:2306.03709 (v1 6 Jun 2023, v2 4 Dec 2023); Nature Physics 20, 1461–1468 (2024). https://arxiv.org/abs/2306.03709 (I read the HTML version: https://arxiv.org/html/2306.03709)
Hua-Liang Liu, Hao Su, Si-Qiu Gong, … Jian-Wei Pan (37 authors), Robust quantum computational advantage with programmable 3050-photon Gaussian boson sampling. arXiv:2508.09092 (v1 12 Aug 2025, v3 24 Aug 2025). https://arxiv.org/abs/2508.09092. I read the v1 HTML: https://arxiv.org/html/2508.09092v1
1. Dodd, Martínez-Cifuentes, Thomson Brown, Quesada, García-Patrón, A fast and frugal Gaussian Boson Sampling emulator. arXiv:2511.14923 (v1 18 Nov 2025). https://arxiv.org/abs/2511.14923; HTML read at https://arxiv.org/html/2511.14923
2. Tong Liu, Hui-Ke Jin, Tao Xiang, Hong-Hao Tu, Efficient simulation of low-entanglement bosonic Gaussian states in polynomial time. arXiv:2512.10643 (v1 11 Dec 2025, v2 11 May 2026); the arXiv page lists npj Quantum Information 12, 110 (2026). https://arxiv.org/abs/2512.10643; HTML read at https://arxiv.org/html/2512.10643
3. Goodman, Dellios, Reid, Drummond, Gaussian boson sampling: Benchmarking quantum advantage. arXiv:2604.12330 (v1 14 Apr 2026). https://arxiv.org/abs/2604.12330; HTML read at https://arxiv.org/html/2604.12330
No, and the mismatch runs both ways.
The current state is therefore a stand-off between untested claims. The hardware says it has beaten every spoofer it tested, and those spoofers predate it. The newest spoofer says it could probably handle the new hardware, but has not tried.
In a one-off dispute, paper A claims something, paper B rebuts it, and you can weigh the two. Here the claims are a moving series:
That means any verdict is a verdict on a pair of papers, not on the field. The honest answer as of November 2026:
The pattern so far suggests that will not be the last word in either direction.
You do not need any of this: the Run button sets it up. These are the exact settings and brief the run uses, for checking it or running it by hand.
Nothing. It searches.
# Map brief — GBS quantum advantage (Jiuzhang)
Paste this whole thing. Nothing to fill in.
**Environment:** `night-shift-map`. The exact settings are on this mission's
page — the env file is the only place they live, so they cannot drift out of
sync with a copy written here.
---
## The job
A series of Chinese photonic quantum computers has claimed
computational advantage through Gaussian boson sampling — producing samples
from a distribution said to be beyond classical reach. Each time, classical
algorithms exploiting the experiment's own photon loss and noise have
narrowed or matched the claimed advantage, and each new machine has in turn
claimed to beat the newest classical method.
Lay out the current state of that cycle as of the most recent hardware claim
and the most recent classical challenge: what precisely the newest classical
method claims to do, what the newest hardware claim says it beats, and
whether the two sides are actually answering the same benchmark or each is
responding to an older round. Say plainly that this dispute has a pattern of
escalation rather than resolution, and note whether that makes "is this
settled" a harder question to answer here than in a single paper-versus-paper
fight.
## Sourcing rules
- Every claim about what someone said needs a citation: title, authors, year,
link, and where in the document it appears (section, figure, page).
- **Open the page.** Do not cite from a search-result snippet. If a page will
not load, say so explicitly and mark that citation as unverified rather than
quietly using the snippet.
- Quote the sentence where each party states its position. One sentence is
enough — do not reproduce passages.
- Where two sources conflict on a matter of fact (a date, a number, who did
what), show both and say they conflict. Do not pick silently.
- If you cannot find a source for something you believe is true, leave it out.
- **"Blocked" and "paywalled" are different facts — say which.** A domain
outside this environment's allowlist means you could not try. A domain that
let you connect and then returned a paywall, login wall, or bot check means
you tried and were refused. Both leave a gap in the record, but only the
second tells the reader the source exists and is readable by someone else.
For every source you could not read, the notes must say which of the two it
was. Where a paywalled paper has a preprint, use the preprint and say you
did.
## Output — two files, and both are required
**1. `output.md`** — the prose, as described above. Write it for a reader.
Structure it however reads best.
Then a section called **Notes on this run** — for me, not for a reader:
what you searched, what failed to load, which citations are unverified, what
you are unsure about, and anything that surprised you. Blunt.
**2. `positions.yaml`** — the same positions as structured data. One entry per
party per claim: a group that disputes two separate things gets two entries,
and two groups making the same claim get one entry each.
```yaml
positions_file:
mission: MAP-009
source: output.md
count: <number of entries below>
positions:
- id: P01
party: <named person or group, as the source names them>
claim: <one line, no hedging>
stake: <employment, funding, or competition — factual, or "none found">
sources:
- url: <url>
read: yes # you opened this page and read the text you cite
- url: <url>
read: no # you know it exists; you did not open it
```
**`read` is not a formality.** A URL you opened and a URL you merely know
exists are the same string, and listing one under `sources` implies you read
it. Say which. `read: yes` is checkable — an opened page leaves a fetch in
this session's transcript, which you do not write — so a `read: yes` with no
fetch behind it is a false record, and worth more scrutiny than an honest
`read: no`. Prefer citing what you read; where you must cite unread, say so
and the reader can weigh it.
**These must agree.** Every position in the prose appears in the YAML and vice
versa. The board counts entries in `positions.yaml` — it never parses your
prose, because a count derived from headings is a count that can silently be
wrong. If you can only produce one of the two files, produce neither and
deposit a finding explaining why.
An unmappable position is still a position: record it with the claim as stated
and `sources: []`, and say in the prose exactly what is missing.
## Where to put them
Push a branch to **`night-shift-network/inbox`** with both files inside a
directory named for this mission:
```
MAP-009/output.md
MAP-009/positions.yaml
```
The directory is what matters. A file at the root of the branch is not a
deposit and will not be collected — it will sit there looking delivered while
nothing has been.
The branch name does not matter and is deliberately not specified: the relay
reads every branch, so whichever branch your session is already on is fine.
Never delete or force-push a branch, yours or anyone else's; cleanup is
maintainer-side only.