wai-quantum: receipts say where their counts come from and what was set at the provider, and a second verifier checks them #660

Merged

dcharlot merged 24 commits from wai/quantum-receipt-fields into main 2026-11-06 14:45:15 -05:00

Conversation 0 Commits 24 Files changed 259 +27034 -955

2026-11-06

Transaction Science

wai-quantum: seal_into passes its function, as clippy asks ...

Co-Authored-By: Claude Opus 5.5 <[email protected]>

fc44eb3445

• View at this point in history

2026-11-06 10:14:07 -05:00

Transaction Science

wai-quantum: the views page built again, its verify without the engine's set re-derivation ...

The page is built from wai-quantum-views, whose verify now holds every rule of
the receipt; through job::verdict it also carried the engine's re-derivation of
a set's sweep, which put the page past its 1 MiB limit. It checks the receipt's
rules alone (job::check), and the page is 984,188 bytes, built on Linux as CI
builds it.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

7e0901bd1f

• View at this point in history

2026-11-06 09:24:37 -05:00

Transaction Science

Merge wai/quantum-cloud-tasks into wai/quantum-receipt-fields ...

Co-Authored-By: Claude Opus 5.5 <[email protected]>

28927d4862

• View at this point in history

2026-11-06 08:54:33 -05:00

Transaction Science

wai-quantum: the views page built again from its sources ...

The Studio's English words for an estimate's minimum ("at least") are among
the page's sources, and the committed page was built before them.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

4d4a5ebba9

• View at this point in history

2026-11-06 08:54:05 -05:00

Transaction Science

wai-quantum: a set's item read for what is sealed, keyed to its set, a failed item's numbers by its leaf; tool lists regenerated ...

An item's key is compared with the set's receipt's key member as it stands. An
item is read for its index, request, result, error and path; what else it
holds is unsealed, and the differential's oracle now says so. A failed item's
numbers are read as a canonical receipt reads them, whatever the set's form,
since its leaf is the canonical form's digest. Two first-form set vectors.
The second verifier, from the text, agrees on all 156 receipts. The service's
and the command line's tool lists are regenerated, signer among the verify
answer's members.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

6d6b774472

• View at this point in history

2026-11-06 07:50:16 -05:00

Transaction Science

wai-quantum: the second review's seven, and a set's receipt in section 8 ...

RFC 8785's spelling of a large whole double is taken; a set's receipt is section
8.6, with three reasons, and every surface judges a set by it; a receipt is
checked on its text in the Studio, the desktop app and the npm example; set
requests are screened; the tools take a job's text; qubit_names covers every
qubit qasm3 acts on; the service's verify schema describes signer. Corpus:
two sets made by the command line, fourteen set vectors, five number vectors,
one names vector; three more plants. Work in progress: its battery is running.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

8436745b66

• View at this point in history

2026-11-06 07:23:03 -05:00

Transaction Science

Merge wai/quantum-cloud-tasks into wai/quantum-receipt-fields ...

Co-Authored-By: Claude Opus 5.5 <[email protected]>

10adefebde

• View at this point in history

2026-11-06 03:20:16 -05:00

Transaction Science

wai-quantum-qpu: cloud-tasks asks after a task where it is, signs as the published suite does, and keeps a list's unknown kinds ...

The second review's six. A list of providers holding a kind this build does
not know is read, the entry kept as it is and noted; the changelog says plainly
that earlier builds cannot read a list holding a cloud-tasks entry. A client
reads a processor's task through the qubits it read only when it submitted the
task; a task's region comes from its id. wai-qpu asks for --yes on anything not
stated free. providers test says "at least" of a minimum. Signing is held to the
published v4 test suite, by both path rules and with a body. The fake service
takes the bucket from the host or the path, walks a task through its states and
a cancel, and writes results in the published result schema's form.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

72f127376b

• View at this point in history

2026-11-06 03:17:24 -05:00

Transaction Science

wai-quantum: the desktop app, the browser and the notebook held to the corpus; qubit_names and whole numbers in it ...

The desktop app's verify and the browser's engine_verify each have a test that
reads the corpus's text and gives section 8.4's reasons. The command line's tool
answers a set as a set, and its schema says so, with signer. The corpus gains
receipts for qubit_names (missing, null, a leading zero, short), a job stated by
nobody on a kind with rows, and whole numbers past 2^53 - 1 with only a count's
value capped, so a ceiling on every whole number is caught by the corpus alone,
as the second-only run in the conformance step needs. The notebook's stored
verdict names its reasons and form. Tool lists and agent docs regenerated.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

7671774f03

• View at this point in history

2026-11-06 02:22:28 -05:00

2026-11-05

Transaction Science

wai-quantum: a set is verified as a set everywhere, a host gives no receipt it would refuse, and the corpus keeps what it holds ...

A surface that takes a job takes a set, and verified it against a seal over its
head as if over the whole result, so a good set read as invalid. The provider
path checks its own receipt before giving it: a provider's word reaches the
seal. A made receipt is pinned by digest, and generate.py --self-test shows each
way the pins fail. The corpus gains two receipts by the first form's own writer,
from the service as it was on 18 October. A second verifier's reading settled
four sentences of section 8, and -0 as an index, where the two disagreed.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

3bec9b4a01

• View at this point in history

2026-11-05 18:21:50 -05:00

Transaction Science

Merge wai/quantum-cloud-tasks into wai/quantum-receipt-fields ...

Co-Authored-By: Claude Opus 5.5 <[email protected]>

41945f54ce

• View at this point in history

2026-11-05 18:03:27 -05:00

Transaction Science

wai-quantum: every verify surface holds every rule, and a host seals nothing its verifier refuses ...

job::verify runs job::check. POST /v1/verify, the service's tool, the command
line's tool and its verify on a set, an estimate or an algorithm's answer, the
Python package, the desktop app and the browser all apply section 8.4, reading
a job's text as text where they hold it, so a member named twice is found. Each
gives reasons beside valid and key, and a set's items are held to a job's rules.

A local host's qec, compile, pulse, estimate, @Seal and intent check now refuse
a request holding a number no double holds, as a run does, and seal_into writes
one in a result as the double sealed. A receipt already sealed with one stays
refused, its signature good, and verifies written as that double's digits.

A job recorded by the last release gets a receipt this one accepts: its program's
text from its record, and execution stated by nobody, which every kind takes.
compiled.qubit_names says which of the device's qubits each index was. sampler-v2
reads a backend's simulator member. The reference's ceiling on every whole number
is gone, as section 8.4 has it, with sums exact, and the differential now tries
numbers past a double's whole numbers, with a plant that proves it can see them.
verify --json keeps --history. The earlier form claims no sealing time. A made
receipt is pinned by digest. R of small order is tested where the equation holds.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

6b947aa379

• View at this point in history

2026-11-05 18:03:27 -05:00

Transaction Science

wai-quantum-qpu: the guide's cloud-tasks example names a region and a bucket that are names ...

The guide's runnable block used an ellipsis for each, which adding a provider now refuses.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

760abf0750

• View at this point in history

2026-11-05 18:02:54 -05:00

Transaction Science

Merge wai/quantum-cloud-tasks into wai/quantum-receipt-fields ...

Co-Authored-By: Claude Opus 5.5 <[email protected]>

951cfd26a1

• View at this point in history

2026-11-05 17:44:33 -05:00

Transaction Science

wai-quantum-qpu: cloud-tasks reads a job through the qubits it was sent on, and refuses what it could not read ...

A job's record keeps the device's own names for its program's qubits, and
collection reads through those without asking the device again. Logical qubits
are read from a row by label, so a qubit past the sixty-fourth can be read, and
one the program ended on that was not measured is an error. Region and bucket
are checked before they go into a host; a dotted bucket is read by path, from
the bucket the task names. An endpoint this kind would not use is refused. A
named credential that gives nothing is an error on every built-in kind, and
every part of the keys comes out of a message, whole or cut short. wai-qpu asks
for --yes wherever a job spends. A simulator's estimate says it is the minimum.
The client now has a fake that follows the service's contract, temporary keys
among what it checks.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

80528577db

• View at this point in history

2026-11-05 17:40:53 -05:00

Transaction Science

wai-quantum: the receipt work on wai-quantum-qpu 0.5.0, and what replaying CI's steps found ...

This follows the merge of #654's new head, and a replay of the workflows' own
steps on Linux.

- The qpu workflow pins each test binary's count. This branch adds two tests
  to the library and one to the clients, so the pins are 63 and 9, and the
  three are named.
- The job service's committed tool list was stale. The receipt and job-result
  schemas changed after it was last regenerated, so the service's own test
  failed. It is regenerated.
- `CountsSource` is `#[non_exhaustive]` and its `ALL` is a slice, by the rule
  #654 applied to `Kind`: a later text may add a source in a minor release.
- The Chinese command-line README now says of a provider's result what the
  English one does.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

b3fdad50a9

• View at this point in history

2026-11-05 16:18:06 -05:00

Transaction Science

Merge wai/quantum-cloud-tasks (#654: main, wai-quantum-qpu 0.5.0, and its CI fixes) into wai/quantum-receipt-fields ...

Co-Authored-By: Claude Fable 5.1 <[email protected]>

7fabdd0fde

• View at this point in history

2026-11-05 16:17:52 -05:00

Transaction Science

quantum-studio: a code's summary, certificate and lattice change in one step ...

The error-correction pane set a new code's summary and decoders, then checked
its seal, then drew its lattice. The browser test waits for the summary and
reads the lattice at once, and on this branch's run it read the surface code's
two faces where the colour code's nine were due. The file is main's, so the
race is on main too; the job passed on the eight other runs around this one.

The seal is now checked first and the pane changes together, as a decode
already did. A threshold had the same split, its plot drawn before the check
and its reading after: with the check slowed by 800 ms the test fails there
too, so it is fixed the same way. With that delay the test fails on main's
ordering and passes on this one. The test is unchanged.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

9db46c96d5

• View at this point in history

2026-11-05 16:11:57 -05:00

Transaction Science

CI: the qpu library's test count, and the keys the guide's cloud-tasks provider reads ...

The qpu workflow pins each test binary's count, and the library's was still 46.
The cloud-tasks client adds 15, so it is 61, and three of its tests are named.

The guide's block that adds a `cloud-tasks` provider reads `keys.txt`, which the
documentation's fixtures did not hold. The block stopped there, so the next
block's `providers remove turns` found no provider. The fixture is added.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

d59daf4c08

• View at this point in history

2026-11-05 15:29:00 -05:00

Transaction Science

wai-quantum-qpu 0.5.0: a new kind and a new method break its API, and are the last to ...

`Kind::CloudTasks` and `Method::Put` were added to exhaustive public enums. That
breaks a downstream `match`, so the API check failed with the crate still at
0.4.1. The crate is now 0.5.0, as VERSIONING.md asks of a breaking change before
1.0, and the command line and the desktop app require it.

`Kind` and `Method` are `#[non_exhaustive]` from this version, and `Kind::ALL` is
a slice. A kind is a value of a list that grows, which a minor release may add
to; with the enum exhaustive, every new kind was a breaking release. Inside the
crate a `match` stays exhaustive.

The changelog entry moves from the head of CHANGELOG.md to a file of wai/changes/
and says what to do instead. The API job's baseline step took the version
`cargo info` selects (`0.4.0 (latest 0.4.1)`) for the last one published and
warned on every run; it now reads the latest.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

876818767b

• View at this point in history

2026-11-05 15:29:00 -05:00

Transaction Science

Merge origin/main (#638, #652: parameter sets, and the relay loop test's ports) into wai/quantum-cloud-tasks ...

Co-Authored-By: Claude Fable 5.1 <[email protected]>

266f690bd4

• View at this point in history

2026-11-05 15:17:56 -05:00

Transaction Science

wai-quantum: receipts say where their counts come from and what was set at the provider, and a second verifier checks them ...

A provider's result now states counts_source (shots, vendor_counts or
probabilities, since counts rebuilt from probabilities are derived) and
execution (what each client set off at the provider, built from the very body
it posts). It labels a simulator's counts simulated rather than measured, and
carries the compiled program's text beside its hash. Receipts sealed before
these fields still verify, and are read by their provenance.

Section 8 of the provider protocol is rewritten so that a verifier can be
written from it alone: the seal byte for byte, the strict reader, the canonical
text and the first form's, strict Ed25519, the per-kind rows, seventeen named
reasons, and what a receipt proves. A second verifier was written in Python
from that text by a reader who had not seen the reference, and its gaps became
the text. The reference had accepted a receipt under a small-order key for any
content, any alg, upper-case or +-spelled hex and duplicate members, and
panicked on a two-byte character in a key; it refuses each now.

A corpus of receipts made by the command line, the job service and every
built-in kind, plus receipts crafted to break one rule each, is judged by both
verifiers on every receipt and every one-member change of each valid one, and
each planted defect must be caught. CI runs it beside the CLI's build.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

265b2f0ffd

• View at this point in history

2026-11-05 15:09:03 -05:00

Transaction Science

wai-quantum-qpu: cloud-tasks as the real service takes it, with the whole charge ...

Running it on the service's simulator showed two things the scripted tests
could not: a program must measure explicitly, and a simulator refuses a register
with a qubit no gate touches. So every program now assigns its measurements, and
a simulator's idle qubits get an identity.

The estimate now includes the service's fee per task, which its API does not
state, so a job on a processor shows what it will cost. And a simulator can
compile to a processor's basis (`--set basis=gpizz`), so the gates can be checked
before paying for the processor.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

fe1c9be9ad

• View at this point in history

2026-11-05 12:07:03 -05:00

Transaction Science

wai-quantum-qpu: a built-in provider kind for a cloud service of quantum tasks ...

`cloud-tasks`: one device on the person's own account. Requests are signed
with their keys (Signature Version 4), and results land in their own storage
bucket. On a processor the program is OpenQASM 3 in a verbatim box on physical
qubits. A device of `rx rz cz` takes the `rzsxxcz` basis, with `sx` and `x` as
`rx`, since they differ only by a global phase. A device whose native gates
fit no basis is refused with what it runs. The estimate gives the device's
price and says the service's per-task fee is left out.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

ba429af757

• View at this point in history

2026-11-05 11:26:47 -05:00