State
Reliable routine
The same routine after the good branch has been amplified, now carrying a failure probability you can quote, a query count, and the sequential depth that buying the reliability consumed.
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
Anything that asks for one of these will accept this, because it is narrower. The reverse does not hold.
- State you can prepare
Not the state itself but the routine that makes it — which is the useful form, because a routine can be run again, controlled, and inverted, and a state that has already collapsed can do none of those.
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
- Amplify a success branch
Take a routine whose output lands in the wanted subspace only with probability , and raise that probability to near 1 using quadratically fewer repetitions than restarting the routine would need.
Work that starts here
No process asks for this by name. The ones below ask for something broader, and this is a kind of it — so they take it as it stands.
Also accepted where something broader is wanted
These ask for an object this one is a kind of. Narrowing composes in that direction and only that direction: handing on something broader than a process asks for would be a skipped conversion.
- Estimate an observable
Given the ability to prepare and a description of an observable , return a classical scalar within of at confidence . The state is never returned; only the number is.