Lattice Surgery
Lattice surgery implements fault-tolerant logical operations by changing which local checks are measured along the boundaries of encoded patches. Its central primitive is not a geometric animation of patches fusing and separating. It is a protected measurement of a joint logical Pauli operator, such as
The interface checks are local even though their decoded product reveals a nonlocal logical parity. Repeating those checks in time protects the parity against measurement faults; maintaining sufficient width around the interface protects it against data faults. Merge, split, routing, CNOT, teleportation, and multi-patch Pauli measurements can all be understood from this one idea.
Lattice surgery is especially natural for planar topological codes on two-dimensional nearest-neighbor hardware. It avoids the pairwise long-range interactions required by a transversal gate between separate patches. That advantage is not free. Surgery consumes boundary length, routing area, syndrome rounds, decoder work, and classical reaction time. A logically correct parity projector is only fault tolerant when the complete spacetime operation retains the declared distance.
Canonical Scope
Section titled “Canonical Scope”Surface Code owns surface-code stabilizers, logical strings, boundary geometry, repeated syndrome extraction, code-specific thresholds, and static patch overhead. The Threshold Theorem owns the general asymptotic theorem, its noise assumptions, and overhead logic. Fault-Tolerant Gates owns the general error-containment contract and compares surgery with transversal, deformation, gauge-fixing, pieceable, and teleportation-based mechanisms. Decoders owns general syndrome inference.
This page is the canonical home for lattice-surgery conventions, rough and smooth merges and splits, joint-parity projectors, the measurement-based CNOT correction table, time-dependent decoding, multi-patch measurements, twist variants, routing, and scheduling. Magic State Distillation owns resource-state purification and factories; surgery supplies many of the logical measurements used inside those protocols.
Experimental statements below use an evidence cutoff of 11 August 2026. The logical constructions are established. Which layouts, decoders, and hardware implementations minimize delivered logical error and spacetime cost remains an active engineering question.
Quantum Error Correction and Fault Tolerance routes here when a protected architecture uses joint logical parity measurements and code deformation; this page retains seam checks, merges, splits, logical CNOT construction, spacetime fault tolerance, decoding, layout, routing, and operation evidence.
Conventions Before Geometry
Section titled “Conventions Before Geometry”Consider a planar CSS patch encoding one logical qubit. We use the standard surface-code naming convention:
- a rough boundary permits a physical string to terminate;
- a smooth boundary permits a physical string to terminate;
- can be represented by a string joining opposite rough boundaries;
- can be represented by an string joining opposite smooth boundaries.
Some diagrams rotate the patch, exchange primal and dual lattices, or swap the words rough and smooth. The operational statement is safer than the nickname: identify the logical product represented by the decoded interface checks. In the convention used here,
| Operation | Interface action | Logical information obtained |
|---|---|---|
| rough merge | prepare seam data in $ | 0\rangleX$-type checks |
| smooth merge | prepare seam data in $ | +\rangleZ$-type checks |
| rough split | measure the separating data row in the basis | creates rough boundaries |
| smooth split | measure the separating data row in the basis | creates smooth boundaries |
The seam preparation commutes with the checks that were already well defined on the separate patches. The newly introduced checks need not have individually predictable first outcomes. Their corrected product carries the logical parity.
The Logical Parity Projector
Section titled “The Logical Parity Projector”For a Pauli product with eigenvalues , encode the measurement outcome as a bit , so the reported eigenvalue is . The ideal projector is
For an input density operator , the outcome probability and normalized post-measurement state are
For a two-patch surgery, set . This measures whether the logical computational-basis labels have equal or unequal parity. It does not measure either logical separately. For example,
while the odd outcome gives
Coherence within one parity sector is preserved in the ideal operation. Revealing which individual patch carried the would destroy that coherence and would not implement the same channel.
The analogous projector distinguishes equal and unequal labels in the Hadamard basis. Joint parity is therefore both a measurement and an entangling resource.
What the Seam Checks Measure
Section titled “What the Seam Checks Measure”Let be the stabilizer group while patches and are separate. During a merge, selected boundary checks are replaced by a set of local interface checks
For the intended geometry, their product is equivalent on the old code space to a joint logical Pauli, up to a known old stabilizer and sign:
If the old stabilizer frame is known, corrected interface eigenvalues yield
The sign includes geometry conventions, old stabilizer eigenvalues, data-measurement outcomes, and tracked Pauli-frame changes. A diagram that says only “multiply the seam checks” is incomplete unless these sign conventions are fixed.
Why repeated rounds are needed
Section titled “Why repeated rounds are needed”The new checks have no reliable comparison value from the preceding static round. A readout fault can flip an interface outcome, and a string of time-directed measurement faults can flip the decoded logical parity without leaving an endpoint inside the observed spacetime window. For a nominal distance- operation, the standard construction runs the merged check set for order syndrome rounds and supplies appropriate temporal boundary conditions to the decoder.
The slogan “run rounds” is a design rule, not a proof. The check circuit, hook orientation, first and last round, reset policy, final data measurement, and decoder graph must together give spacetime distance at least for both data preservation and the reported parity.
Rough and Smooth Merges
Section titled “Rough and Smooth Merges”A merge changes two encoded patches into one larger stabilizer code while recording one logical parity bit. The quantum degree of freedom conjugate to that parity is projected. The classical outcome plus the remaining encoded degree of freedom account for the information after measurement.
Rough merge: logical XX
Section titled “Rough merge: logical XX”Place rough boundaries of patches and along an interface. Prepare any new seam data qubits in , then introduce the prescribed -type checks spanning the interface. After the time-dependent syndrome is decoded, their corrected product gives
The ideal logical action is the projector
The child patch’s logical may be represented by a product of parent logical strings, while its logical can be represented by either parent string after a frame convention is chosen. Exact representatives depend on orientation and on which boundary checks were replaced.
Smooth merge: logical ZZ
Section titled “Smooth merge: logical ZZ”Place smooth boundaries along the interface. Prepare new seam data in and introduce the corresponding -type interface checks. Their corrected product gives
with projector
The and roles are exchanged relative to a rough merge. In both cases, individual new-check outcomes can be random even when the logical product is deterministic.
A merge is not a unitary gate
Section titled “A merge is not a unitary gate”Two encoded qubits enter a merge and one encoded degree of freedom remains in the child patch. The missing quantum degree has become a classical measurement outcome. A subsequent split can return to two patches, but it does not restore coherence between parity sectors erased by the measurement. A merge followed by a split is a protected parity measurement, not the identity channel.
Rough and Smooth Splits
Section titled “Rough and Smooth Splits”A split removes a row of data qubits and restores two separately stabilized patches. The measurement outcomes determine new boundary stabilizer signs and logical frames. After decoding and frame updates, the ideal action is an isometry from one logical qubit into a correlated two-qubit subspace.
Smooth split
Section titled “Smooth split”Measure the separating row in the basis to create smooth boundaries. Ignoring a known byproduct, the logical isometry is
Thus
The logical-operator map is
The output lies in the eigenspace of . Starting from therefore prepares a logical Bell state, up to the tracked frame.
Rough split
Section titled “Rough split”Measure the separating row in the basis to create rough boundaries. In the Hadamard basis, the ideal isometry is
Its operator map is
This is not cloning. The daughters are generally entangled, and neither reduced state equals an arbitrary pure input state.
Distance during a split
Section titled “Distance during a split”The mother patch must be large enough that each daughter retains the target distance. Splitting a square distance- patch through its middle can create a short logical path of order . To produce two distance- daughters, one commonly starts from an elongated patch with transverse dimensions chosen for both outputs. Corners, disabled checks, and the measurement row must be included when finding the shortest logical path.
One convention for a measurement-based logical CNOT. Each parity box denotes a fault-tolerant, decoded lattice-surgery operation lasting multiple syndrome rounds, not an instantaneous two-qubit measurement. The final frame is .
A Logical CNOT from Parity Measurements
Section titled “A Logical CNOT from Parity Measurements”Let be the control, the target, and prepare an ancilla logical qubit in . Perform, in order:
- measure , obtaining bit ;
- measure , obtaining bit ;
- measure , obtaining bit .
The measurements can be implemented by smooth and rough surgery with an ancilla or routing patch. The logical derivation does not depend on the microscopic layout.
Deriving the byproducts
Section titled “Deriving the byproducts”Let
The Kraus operator acting on and is
Using
one obtains, up to an outcome-dependent global phase,
The physical measurement branch therefore produces the desired CNOT followed by known Pauli byproducts. They may be applied or, more commonly, recorded in a logical Pauli frame.
| frame update | |||
|---|---|---|---|
| 0 | 0 | 0 | none |
| 0 | 0 | 1 | |
| 0 | 1 | 0 | |
| 0 | 1 | 1 | |
| 1 | 0 | 0 | |
| 1 | 0 | 1 | none |
| 1 | 1 | 0 | |
| 1 | 1 | 1 |
Different ancilla preparations, measurement orderings, bit conventions, or choices of output frame produce different-looking tables. A protocol must state its circuit before quoting corrections. The invariant content is that the branch differs from CNOT by a known Clifford, here a Pauli.
Logical schedule versus patch schedule
Section titled “Logical schedule versus patch schedule”At the logical level the construction contains two sequential parity measurements and one destructive ancilla measurement. In a patch layout, each parity measurement expands into seam preparation, a time-dependent check schedule, order- syndrome rounds, decoding, and frame extraction. Patch initialization, split operations, movement, and final boundary restoration may add cycles. Quoting “two measurements” is not a physical runtime estimate.
Fault Tolerance Is a Spacetime Property
Section titled “Fault Tolerance Is a Spacetime Property”Static patch distance does not certify a surgery. Let be the set of fault chains that cause either an incorrect logical output or an incorrect reported parity while producing no distinguishable detector pattern. Define the operation distance
A distance- protocol aims for under its declared circuit-level fault model. Three broad classes of minimal chain must be checked:
- spacelike chains cross a patch, interface, neck, or routing strip;
- timelike chains corrupt enough repeated measurements to flip the logical parity;
- mixed chains use data, hook, measurement, leakage, and boundary faults along a diagonal path through the transition.
The shortest chain can change when a check is turned on or off. A neck that looks qubits wide in one drawing may have a shorter diagonal path in the actual CNOT schedule. Corners and twists can create high-weight checks whose ancilla faults spread differently from bulk checks.
For a local stochastic circuit model, one often fits a surgery failure rate to a form such as
This is a model-dependent scaling ansatz, not a universal law. The prefactor, threshold, effective distance, and even the relevant scalar physical error depend on the check circuit, decoder, leakage handling, bias, and observable being benchmarked.
Hook errors and check order
Section titled “Hook errors and check order”An ancilla fault during a multi-data-qubit check can propagate to a correlated data error. The order of two-qubit gates should orient these hooks so they do not shorten a logical path. At a changing boundary, a schedule safe for the static bulk may be unsafe: elongated checks, half checks, and twist checks have different supports. A circuit-level surgery specification must publish the gate order, not only the stabilizer generators.
First and last rounds
Section titled “First and last rounds”The first interface-check outcomes establish new gauge or stabilizer values. The last rounds must connect those values to the restored patches or to final data measurements. If the decoder simply compares every check with a nonexistent previous value, it invents detectors; if it drops the temporal boundary, a measurement-error chain may escape.
Fault tolerance can be understood as a gauge-fixing process. The separate, merged, and split descriptions select different commuting subsets of an enlarged gauge group. That algebra explains why the logical channel is well-defined. It does not replace the spacetime circuit and decoder proof.
Decoding a Changing Stabilizer Code
Section titled “Decoding a Changing Stabilizer Code”For a persistent check with measured signs , a simple detector is a change between rounds,
At a merge or split, some checks appear, disappear, or change support. Transition detectors can combine:
- old boundary-check outcomes;
- first-round interface outcomes;
- single-qubit seam measurements;
- restored boundary checks;
- final data measurements;
- known preparation and Pauli-frame signs.
The decoder should output more than a data correction. It must also estimate the logical parity bit, any boundary-frame changes, and confidence or heralding information needed by the controller. In a detector-error-model description, the parity is a logical observable whose sign can be flipped by certain faults; decoding chooses which compatible fault class is most likely.
Streaming and windows
Section titled “Streaming and windows”A large processor cannot wait until the entire computation ends before decoding every surgery. Sliding-window or parallel-window decoders pass boundary information between time windows. Their overlap must be long enough that a fault chain crossing a window boundary is not cut into two harmless pieces. A favorable mean decoder latency is insufficient when an adaptive measurement basis depends on the parity; tail latency can stall the quantum schedule.
Soft information and erasures
Section titled “Soft information and erasures”Analog readout likelihoods, heralded leakage, atom loss, and flagged hook events can improve inference when the decoder model accepts them. Their value is conditional on calibration. An incorrect erasure flag or stale readout likelihood is itself a noisy observation and must be represented in the detector model.
Multi-Patch Pauli Measurements
Section titled “Multi-Patch Pauli Measurements”The two-patch operators and generalize to
An ancilla region or routing strip can touch the appropriate boundary of each participating patch. Local checks along the combined interface are repeated and decoded; their corrected product reports the eigenvalue of . This measurement language is often more efficient than decomposing every logical operation into pairwise CNOT gates and then routing those gates independently.
Increasing the Pauli weight does not automatically require serial time proportional to : separated interfaces may be checked in parallel. However, the ancilla region grows, more corners and routes are exposed, and there are more ways for correlated faults to affect the result. The complete spacetime distance and logical failure probability still depend on and geometry.
Mixed boundaries and Y factors
Section titled “Mixed boundaries and Y factors”Pure products of operators can meet -accessible boundaries, and pure products can meet -accessible boundaries. A mixed Pauli product may require an ancilla patch whose boundary type changes along its perimeter. The change point is a twist defect or domain-wall endpoint.
Since
a logical factor involves both boundary types and a phase convention. Twist-based lattice surgery supplies local checks around the junction, but those checks can have unusual weight and connectivity. Circuit-level studies find that a good twist schedule can retain useful performance, yet it cannot be assumed equivalent to an ordinary or seam.
Alternatives include rotating a patch boundary, decomposing the measurement, using temporal encodings, or adopting a twist-free construction. These move cost among extra rounds, ancilla space, connectivity, and classical tracking. The appropriate comparison is at fixed delivered logical error.
What Surgery Can Build
Section titled “What Surgery Can Build”Bell and GHZ states
Section titled “Bell and GHZ states”A smooth split implements
up to a frame. Repeating compatible splits creates a logical GHZ state, provided the mother patch is large enough for every daughter to retain the target distance. The Hadamard-basis counterpart follows from rough splits.
Teleportation and movement
Section titled “Teleportation and movement”Joint and measurements, logical single-qubit measurements, and prepared ancillas implement encoded teleportation. Information can therefore move through an ancilla channel without physically translating every data qubit. The output location, Pauli frame, route occupancy, and decoder reaction become part of the teleportation contract.
Patch deformation can also move or rotate a patch by adding qubits on one side and measuring them out on another. Calling this “free movement” hides the repeated syndrome rounds and temporary reduction in geometric clearance.
Resource-state consumption
Section titled “Resource-state consumption”Magic-state injection and distillation circuits can be compiled into multi-patch Pauli measurements. Surgery then acts as the data-plane interface between a resource factory and an algorithm. The factory’s output rate is useful only if routing strips and injection ports can deliver states without blocking data patches. Magic State Distillation owns the resource quality and factory service contract.
Clifford tracking
Section titled “Clifford tracking”Many logical Pauli and Clifford corrections can be tracked classically. Tracking changes how future patch boundaries and measurement bases are interpreted; it does not erase all control dependencies. A tracked Hadamard, for example, exchanges the meanings of logical and . The scheduler must know which physical boundary currently realizes each tracked operator.
Layout, Routing, and Spacetime Cost
Section titled “Layout, Routing, and Spacetime Cost”Representing a distance- patch as one square “tile” and a distance-protected operation as one logical time step is useful for architecture sketches. It is an abstraction. Let
be the active physical-qubit area of one patch and let
be one surgery duration. A local constant-size operation then has leading qubit-cycle volume
with constants set by the layout, check schedule, ancillas, and whether preparation or restoration overlaps other work.
For a routing strip of physical length and protected width of order ,
if local checks along the strip run in parallel for order cycles. If the separation is logical tiles, then and the volume is . A long-range parity measurement can therefore have distance roughly independent time while still paying distance-dependent area and volume.
Compact and fast layouts
Section titled “Compact and fast layouts”A compact data block exposes few patch boundaries to routing space and uses less area, but serializes many measurements. A fast layout exposes more boundaries and keeps larger ancilla corridors, allowing several commuting measurements in parallel. Intermediate layouts trade area for reaction depth.
The best point depends on the scheduled workload, not only the logical gate count. Two circuits with the same number of CNOTs can have different route contention, Pauli-measurement parallelism, and factory demand.
Resource accounting
Section titled “Resource accounting”A reproducible surgery estimate should distinguish:
and should report:
- active and reserved patch area;
- syndrome-cycle duration;
- operation-specific round counts;
- route and turn widths;
- parallel seam capacity;
- decoder and feedforward latency;
- leakage-removal and reset cycles;
- failed preparation or postselection cost.
Resource Estimation owns the end-to-end workload model that composes these terms; Resource Estimation Tools owns the software workflow and reproducibility record.
Failure Modes That Diagrams Hide
Section titled “Failure Modes That Diagrams Hide”Wrong boundary convention
Section titled “Wrong boundary convention”Swapping rough and smooth labels without checking the interface-check product turns an intended measurement into , or vice versa. Define the logical strings and derive the measured product.
Narrow necks and corners
Section titled “Narrow necks and corners”A patch may have nominal width away from the seam but a shorter logical path around a corner, defect, disabled coupler, or ancilla corridor. Compute distance on every intermediate code.
Timelike parity flips
Section titled “Timelike parity flips”Repeated data correction can succeed while a vertical chain of measurement faults flips the classical parity bit. Benchmark the logical measurement observable, not only final data errors.
Unsafe hook orientation
Section titled “Unsafe hook orientation”A single ancilla fault can spread along a logical direction when the gate order changes at the seam. Include the exact extraction circuit in distance and threshold studies.
Leakage across repeated checks
Section titled “Leakage across repeated checks”A leaked ancilla or data qubit can corrupt several rounds and several seam neighbors. Leakage reduction, erasure conversion, and rejected runs belong in the logical channel and throughput accounting.
Frame and sign mismatches
Section titled “Frame and sign mismatches”The product of raw seam outcomes is not necessarily the logical answer. Preparation signs, split measurements, prior Pauli frames, and decoder corrections can all flip it.
Decoder handoff failures
Section titled “Decoder handoff failures”Running a static decoder independently before, during, and after surgery can miss chains crossing the transition. Use one time-dependent detector model or prove a valid handoff rule.
Average-rate scheduling
Section titled “Average-rate scheduling”Enough average ancilla area does not prevent a burst of commuting measurements from contending for the same corridor. Compile routes and deadlines, not only counts.
Experimental Status
Section titled “Experimental Status”The evidence establishes increasingly complete pieces of lattice surgery, but the code family, protected error channels, postselection, and operation scale differ.
| Result | What was demonstrated | Important boundary |
|---|---|---|
| Erhard et al. (2021) | Entangling encoded logical qubits by lattice-surgery-style measurements on a trapped-ion processor | Small perfect-code blocks, not a scalable surface-code patch array |
| Ryan-Anderson et al. (2024) | High-fidelity logical teleportation using transversal gates and lattice surgery with real-time error correction | Bounded trapped-ion code experiment, not distance scaling of a surface-code seam |
| Lacroix et al. (2025) | Logical teleportation between distance-three color codes, alongside distance-three-to-five memory scaling | The surgery operation itself was bounded; memory scaling does not automatically establish surgery scaling |
| Bluvstein et al. (2026) | Ancilla-mediated logical product measurement in a neutral-atom architecture and comparison with transversal logic | Small logical blocks and specified rounds; not a sustained routed surface-code workload |
| Besedin et al. (2026) | A split of one distance-three surface-code patch into two distance-three repetition-code outputs with logical process characterization | Fault tolerant against bit flips in the declared circuit, but phase errors were not protected after the split |
| Wang et al. (2026 preprint) | Operations between two distance-three surface-code logical qubits, logical Bell preparation, a small algorithm, and resource-state injection on superconducting hardware | Preprint evidence; leakage rejection, postselection, small distance, and no increasing-distance operation scaling |
These results support the physical reality of joint logical measurements, splits, teleportation, and bounded logical workflows. As of the cutoff, they do not establish a full surface-code lattice-surgery fabric with increasing operation distance, sustained route throughput, real-time decoding, and algorithm-scale delivered logical error. That stronger claim requires all of those elements together.
Reporting Checklist
Section titled “Reporting Checklist”A lattice-surgery protocol or experiment should report:
- patch geometry, boundary convention, and logical operator representatives;
- separate, transition, merged, and restored stabilizer sets;
- exact seam-data preparations and measurement bases;
- check-extraction circuit and two-qubit gate order;
- number and timing of syndrome rounds;
- detector definitions at first and last transition rounds;
- decoder, weights, windowing, latency, and use of soft information;
- formula mapping corrected physical outcomes to each logical parity bit;
- Pauli or Clifford frame update table;
- operation distance for data and measurement failures;
- circuit-level noise, leakage, erasure, crosstalk, and drift assumptions;
- logical process metric, uncertainty, postselection, and acceptance;
- data, ancilla, route, and buffer area plus qubit-cycle volume;
- which conclusions are proofs, simulations, component demonstrations, or integrated workload evidence.
Common Mistakes
Section titled “Common Mistakes”Calling a merge a CNOT
Section titled “Calling a merge a CNOT”A merge measures one joint parity and reduces the encoded quantum degree of freedom. A CNOT requires a sequence of parity measurements, an ancilla measurement, and frame updates.
Treating split as cloning
Section titled “Treating split as cloning”The split isometry distributes logical operators across two correlated patches. It does not create two independent copies of an unknown state.
Assuming d rounds proves distance d
Section titled “Assuming d rounds proves distance d”The temporal length is only one part of . Hooks, corners, first and last rounds, and decoder boundaries can create shorter fault chains.
Multiplying raw seam outcomes
Section titled “Multiplying raw seam outcomes”The logical sign includes decoded corrections and known frame factors. Raw products can be wrong even in an otherwise correct run.
Equating local time with zero distance cost
Section titled “Equating local time with zero distance cost”A long routing strip can be checked in parallel, but its protected width, area, and spacetime volume grow with separation.
Comparing postselected and deterministic channels
Section titled “Comparing postselected and deterministic channels”Postselection may improve conditional fidelity while lowering throughput. Report acceptance and compare channels under a common service contract.
A Practical Protocol Workflow
Section titled “A Practical Protocol Workflow”- Declare the logical channel. Specify the parity projector, outcome bit, output patches, and frame convention.
- Fix boundary geometry. Draw logical representatives on every patch and verify the product of interface checks algebraically.
- Enumerate stabilizer transitions. Check commutation, encoded dimension, and operator maps at every merge and split.
- Choose extraction circuits. Orient hooks and include reset, leakage, and connectivity constraints.
- Build the detector model. Define transition detectors, logical observables, and window handoffs.
- Audit operation distance. Search spacelike, timelike, and mixed fault chains in the full spacetime circuit.
- Derive every branch. Produce the parity-sign and frame-update tables from the stated circuit.
- Compile the layout. Reserve routes, turns, buffers, and parallel seams under a real workload trace.
- Validate at circuit level. Compare analytic checks, fault enumeration, simulation, and hardware data without changing the accounting boundary.
Connections
Section titled “Connections”- Surface Code supplies the patch stabilizers, boundary strings, and static memory model.
- Color Codes owns triangular colex patches, color-boundary logical representatives, and bounded teleportation evidence; this page retains parity measurements, seams, spacetime decoding, schedules, and routing.
- Fault-Tolerant Gates places surgery inside the ideal-decoder containment contract.
- Decoders develops detector models, correlated-noise inference, windows, latency, and confidence.
- Quantum Software Stack connects logical parity schedules to routing and real-time classical control.
- Magic State Distillation uses protected Pauli measurements to purify and consume non-Clifford resources.
- Fault-Tolerant Quantum Computing Frontier maintains the dated system-level evidence and open integration milestones.
Exercises
Section titled “Exercises”1. A parity measurement is not two measurements
Section titled “1. A parity measurement is not two measurements”Apply an ideal measurement to . Find both conditional states and show that measuring on each qubit separately would implement a different channel.
Solution
Since
the even and odd projectors give, after normalization,
Each occurs with probability . Separate measurements reveal one of the four basis strings and destroy coherence between and , or between and . Forgetting the individual outcomes gives a mixture, not either Bell state.
2. Derive the smooth-split operator map
Section titled “2. Derive the smooth-split operator map”For and , verify the maps of logical and .
Solution
On either basis state,
and the same holds for . Also,
Therefore
One input logical operator becomes a two-output correlation, which is why the split does not clone an arbitrary state.
3. Derive the CNOT frame
Section titled “3. Derive the CNOT frame”For the parity-measurement CNOT convention on this page, evaluate the ancilla matrix elements and recover the byproduct exponents.
Solution
The required matrix elements are
Substitution into the two projectors yields
Comparing with the Pauli expansion of CNOT gives
up to global phase. The two frame bits are therefore for and for .
4. Find the timelike vulnerability
Section titled “4. Find the timelike vulnerability”An interface parity is inferred from repeated noisy rounds. Explain why a single-round protocol cannot have distance against measurement error, even if both patches retain spatial distance .
Solution
With one round, one readout or check-ancilla fault can flip an interface outcome. If that outcome contributes to the logical product, the reported parity can change without a later comparison that creates a detector. The measurement observable therefore has timelike distance one.
Repeated rounds create temporal redundancy: changes in a persistent check produce detector events, and a parity-flipping fault chain must extend to a temporal boundary or connect compatible defects. Achieving distance still requires correct first and last boundary conditions and a circuit whose hooks do not create a shorter mixed path.
5. Estimate long-route volume
Section titled “5. Estimate long-route volume”A protected ancilla strip has physical length , width , and runs for cycles. Ignore constants. Compare its qubit-cycle volume with one patch stored for cycles.
Solution
The strip area is
so its volume is
The stored patch has volume
The route costs forty times the leading volume of one patch over the same duration. Parallel local checks can keep the route time at order , but do not make its area or volume independent of separation.
6. Audit a split geometry
Section titled “6. Audit a split geometry”A square distance- patch is split exactly in half, producing two rectangular daughters whose new transverse width is approximately . Can the operation be advertised as two distance- outputs?
Solution
No. Code distance is the shortest nontrivial logical path in each intermediate and output geometry. If a daughter has a valid logical string of length near , its distance is at most that value regardless of the mother’s original label. To obtain two distance- daughters, the mother needs sufficient extent in the split direction, and the seam, corners, and disabled checks must be included in the path search.
7. Diagnose a decoder handoff
Section titled “7. Diagnose a decoder handoff”A controller decodes static patch rounds, discards its state, and starts a fresh decoder when the merge begins. What information can be lost?
Solution
A fault chain can begin before the merge and end on an interface detector after the merge. Discarding the old decoder boundary conditions can make each piece look locally harmless or can assign the wrong old stabilizer sign. The lost information includes pending defects, likelihoods, frame signs, leakage flags, and correlations crossing the transition.
A valid implementation uses one time-dependent detector model or passes a well-defined sufficient boundary state between windows. The handoff must preserve both data-correction and logical-parity information.
8. Classify an experimental claim
Section titled “8. Classify an experimental claim”An experiment splits a distance-three surface-code patch into two distance-three repetition-code outputs. It corrects bit flips but cannot detect output phase flips. Which claim is justified?
Solution
It demonstrates a lattice-split building block and can establish fault-tolerant behavior for the protected bit-flip fault set, together with whatever logical process metrics were actually measured. It does not demonstrate a fully fault-tolerant two-output surface-code surgery, because arbitrary single-qubit errors include phase errors that the repetition-code outputs do not protect. The code, protected channels, postselection, and reference comparison must remain in the claim.
References
Section titled “References”- C. Horsman, A. G. Fowler, S. Devitt, and R. Van Meter, “Surface code quantum computing by lattice surgery,” New Journal of Physics 14, 123011 (2012), doi:10.1088/1367-2630/14/12/123011.
- H. Bombin and M. A. Martin-Delgado, “Quantum measurements and gates by code deformation,” Journal of Physics A 42, 095302 (2009), doi:10.1088/1751-8113/42/9/095302.
- A. G. Fowler, M. Mariantoni, J. M. Martinis, and A. N. Cleland, “Surface codes: Towards practical large-scale quantum computation,” Physical Review A 86, 032324 (2012), doi:10.1103/PhysRevA.86.032324.
- D. Litinski and F. von Oppen, “Lattice surgery with a twist: simplifying Clifford gates of surface codes,” Quantum 2, 62 (2018), doi:10.22331/q-2018-05-04-62.
- D. Litinski, “A game of surface codes: large-scale quantum computing with lattice surgery,” Quantum 3, 128 (2019), doi:10.22331/q-2019-03-05-128.
- N. de Beaudrap and D. Horsman, “The ZX calculus is a language for surface code lattice surgery,” Quantum 4, 218 (2020), doi:10.22331/q-2020-01-09-218.
- C. Vuillot, L. Lao, B. Criger, C. García Almudéver, K. Bertels, and B. M. Terhal, “Code deformation and lattice surgery are gauge fixing,” New Journal of Physics 21, 033028 (2019), doi:10.1088/1367-2630/ab0199.
- C. Chamberland and E. T. Campbell, “A circuit-level protocol and analysis for twist-based lattice surgery,” Physical Review Research 4, 023090 (2022), doi:10.1103/PhysRevResearch.4.023090.
- C. Chamberland and E. T. Campbell, “Universal quantum computing with twist-free and temporally encoded lattice surgery,” PRX Quantum 3, 010331 (2022), doi:10.1103/PRXQuantum.3.010331.
- D. Herr, F. Nori, and S. J. Devitt, “Optimization of lattice surgery is NP-hard,” npj Quantum Information 3, 35 (2017), doi:10.1038/s41534-017-0035-1.
- A. Erhard et al., “Entangling logical qubits with lattice surgery,” Nature 589, 220–224 (2021), doi:10.1038/s41586-020-03079-6.
- C. Ryan-Anderson et al., “High-fidelity teleportation of a logical qubit using transversal gates and lattice surgery,” Science 385, 1327–1331 (2024), doi:10.1126/science.adp6016.
- N. Lacroix et al., “Scaling and logic in the colour code on a superconducting quantum processor,” Nature 645, 614–619 (2025), doi:10.1038/s41586-025-09061-4.
- D. Bluvstein et al., “A fault-tolerant neutral-atom architecture for universal quantum computation,” Nature 649, 39–46 (2026), doi:10.1038/s41586-025-09848-5.
- I. Besedin et al., “Lattice surgery realized on two distance-three repetition codes with superconducting qubits,” Nature Physics 22, 189–194 (2026), doi:10.1038/s41567-025-03090-6.
- Y. Wang et al., “A superconducting surface-code processor with lattice-surgery logical operations” (2026), arXiv:2606.06598.