State
Logical qubits
Qubits good enough to run the circuit above, together with the code and code distance chosen for them, the physical-per-logical ratio that bought it, and the decoding latency the machine has to keep up with.
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
- Build logical qubits at a target logical error rate
Encode physical qubits whose error rate sits below a code- and decoder-specific threshold into logical qubits meeting a target logical error rate per round, by spending qubits and time on redundancy and decoding syndromes in real time. Which code sits underneath reaches the layers above only as a physical-qubit count and a demand on connectivity.
Work that starts here
No recorded process takes this as its input. Nothing in this graph leaves from here.