Photonic MOC

Curated map of Zoo entries in the Photonic family.

Entries

Entry	Type	Status
fusion-based-photonic-qubit	architecture	proposed
linear-optical-photonic-qubit	architecture	demonstrated
photonic-cluster-state-mbqc-qubit	architecture	demonstrated
dual-rail-photonic-qubit	qubit	demonstrated
frequency-bin-photonic-qubit	qubit	demonstrated
photonic-qubit	qubit	demonstrated
polarization-photonic-qubit	qubit	demonstrated
time-bin-photonic-qubit	qubit	demonstrated
continuous-variable-photonic-qubit	qumode	demonstrated

Composition

• architecture: 3
• qubit: 5
• qumode: 1

Curated synthesis

The highest-value organizing move in this family is to separate photonic encodings from photonic computation models. Otherwise the graph quietly conflates “what degree of freedom stores the qubit?” with “how do we actually get entangling power and fault tolerance?”

1. Encodings optimized for different physical routes

   • dual-rail-photonic-qubit is the canonical chip-scale / LOQC encoding when spatial modes and integrated interferometers are the native hardware language.
   • time-bin-photonic-qubit is the fiber-native encoding when long-distance stability and network transport matter more than on-chip rail geometry.
   • polarization-photonic-qubit is the most direct single-photon Bloch-sphere encoding, with compact wave-plate control but polarization drift in deployed links.
   • frequency-bin-photonic-qubit uses discrete spectral modes and is especially natural for electro-optic control, dense multiplexing, and frequency-comb hardware.
   • These should be read together through erasure-error-vs-pauli-error and noise-bias-and-asymmetric-error-channels: all are loss-dominated photonic qubits, but they package mode matching and phase-stability constraints very differently.

2. Continuous-variable photonics is a different information model

   • continuous-variable-photonic-qubit is correctly typed as a qumode, not a discrete qubit. Gaussian gates are deterministic and time multiplexing reaches enormous mode counts, but universality and fault tolerance require non-Gaussian resources such as GKP states.
   • Route from it to bosonic-code-hierarchy when the question becomes how a continuous oscillator is converted into a protected logical qubit.

3. Gate-based linear optics is an architecture, not an encoding

   • linear-optical-photonic-qubit is the KLM lineage: minimal interactions, heavy ancilla and feed-forward overhead.
   • It usually rides on encodings like dual-rail-photonic-qubit, but the conceptual payload is architectural: probabilistic optics plus teleportation still clear the threshold-theorem barrier in principle.

4. Resource-state / measurement-first photonics is the modern scaling branch

   • photonic-cluster-state-mbqc-qubit shifts the burden from online gates to offline cluster-state preparation plus adaptive measurement.
   • fusion-based-photonic-qubit goes one step further and treats failed entangling attempts as an architectural primitive rather than an exception.
   • Both belong in the same fault-tolerance conversation because they live or die on whether loss and fusion failures stay structured enough for erasure-aware decoding and percolation-style thresholds.

Where the umbrella note belongs

• photonic-qubit should be the family entry point, not a peer competitor to the more specific notes. Use it when the question is simply why photons are attractive at all: low transport decoherence, room-temperature optics, and natural network compatibility.
• Hand off from photonic-qubit to dual-rail-photonic-qubit, time-bin-photonic-qubit, polarization-photonic-qubit, or frequency-bin-photonic-qubit when the real comparison is the discrete encoding degree of freedom.
• Hand off to continuous-variable-photonic-qubit when the carrier is an oscillator quadrature rather than a two-level single-photon subspace.
• Hand off from photonic-qubit to linear-optical-photonic-qubit, photonic-cluster-state-mbqc-qubit, or fusion-based-photonic-qubit when the real comparison is the scaling architecture.
• Once the question stops being optical-hardware-specific and becomes, “what does flagged loss buy the decoder?”, cross over to cross-platform-moc through erasure-qubit instead of repeating decoder logic inside this family.