What was this quantum result made of?
One signed bill of materials answers.
An operations stack runs the job — submits the program, manages the device, returns the counts. What it does not do is sign what the result is made of: which compiled circuit ran (and that it was equivalent to the source), against which calibration, on a register prepared how, under which error mitigation, with which decode. Each of those stages already emits a signed receipt here.
A Quantum Bill of Materials assembles the stage receipts of one computation into a single signed, content-addressed provenance manifest — with a total-energy roll-up and an operator-envelope export a job/result exchange can carry. Verification is layered: the bill verifies its own signature and provenance root, and presented with the actual receipts, it confirms every listed stage binds a receipt that itself verifies — so a swapped or forged stage breaks the bill. Byte-exact and reproducible: the same computation rebuilds the same root from the git repo. The synthesis of the whole quantum-ops receipt family.
The bill of materials · five signed stages, one manifest
The certificate is real · operator-envelope sidecar
A quantum result that carries its own provenance — signed, energy-accounted, verifiable
The bill panel runs two stages on the site's live solvers — a circuit routed onto a coupling graph
and proven equivalent, and a stochastic trap load rearranged defect-free — and bundles
them with a calibration, an error mitigation, and a decode, each a signed stage receipt. The manifest
lists every stage by (kind, receipt hash, joules), rolls up the total energy, and is
itself signed; its provenance root is a content hash anyone can recompute. The second panel
shows the check has teeth — swap one stage for a forgery and the bill no longer binds — and prints
the operator envelope, the provenance sidecar a job/result exchange can carry alongside the
operations stack's own record. A quantum result you can hand an auditor with one verifiable statement
of everything it was made of and what it cost, reproducible from the git repo. Reference manifest +
spec in the open-standards repo, Apache-2.0.