State
Noisy expectation value
What the hardware actually returned, biased by the noise it ran under. It is a measurement, not an error — treating it as the answer is the mistake, and every mitigation method exists to undo a modelled part of the bias.
A state is an object you can be holding, named once so that two routes reaching the same thing are drawn as reaching the same thing. It says nothing about how you got here or where you can go next — that is entirely in the processes below.
This is a kind of
This state is not recorded as a kind of anything else. It stands on its own in the vocabulary.
Narrower kinds of this
No state in the vocabulary is recorded as a narrower kind of this one.
Records that are this object
Nothing in the catalogue has been joined to this state. That is a gap in the join rather than a claim that no such object exists; the shelf on /repository lists what is joined and what is not, with the reason.
Work that arrives here
No recorded process returns this. Either it is where a reader starts — a problem, a matrix, a machine — or it is an object this graph names and no route yet reaches.
Work that starts here
- Recover a noiseless expectation value by post-processing
Estimate what an observable would have measured on a noiseless device by running modified or repeated circuits on the noisy one and combining the results classically. No qubits are spent on redundancy; the whole price is paid in shots.