Checking speed, lift control, and code must be chosen jointly

PDF p. 5: Discussion, final paragraph

The article's platform-design conclusion is that a monolithic code relying on degenerate error processes must be considered together with the control of stray fields that set the lifting strength and the speed of syndrome extraction. A monolithic code stores logical information in the levels of one physical system. Degeneracy lifting separates energies that were equal in an ideal model; its strength describes the size of the modeled shifts. An error syndrome is an outcome used to identify a correctable error class, and syndrome extraction is the procedure producing that outcome. Which-path information is environmental information that can distinguish decay paths. The article's picture is that fast checking extracts the syndrome before appreciable which-path information accumulates.

For a specified code, accumulated noise and recovery, the operational checking time at target fidelity $F_0\in (0,1]$ is the infimum of elapsed times at which the recovered entanglement fidelity falls strictly below $F_0$, with value $+\mathrm{\infty }$ if that set is empty. Entanglement fidelity here measures preservation of a maximally entangled logical input and reference by the recovered logical channel. The article states that the code and lifting strength together set this scale and that protection survives only if syndromes are extracted faster. This is its qualitative design conclusion; the first-crossing definition alone does not prove a universal necessary condition or a bound for a sequence of checks.

Given: The stated definitions, hypotheses and cited interfaces.

Goal: Justify the stated construction and its scope.

1.1 The definition in [F1] makes a threshold comparison meaningful only after the code, noise, recovery and target have been fixed. The code-dependent comparison in [F6] illustrates why changing the encoding can change the reported scale in a specified model. It does not establish the reported numerical ordering beyond that model or independently validate the numerical calculation. [given, F1, F2, F3, F4, F5, F6, F7]

2.1 The repeated-check conclusions in [F2] and [F3] provide conditional support for the fast-checking design picture, with their different recovery protocols and hypotheses kept explicit. In particular, the fixed-$T$ limit in [F3] uses calibrated phase compensation and fixed jump operators as in [F4]–[F5]; it is not a claim that an arbitrary check interval below a first-crossing time guarantees protection. The coefficient in [F2] is an asymptotic statement, not a finite-interval error certificate without a remainder bound. [F1, F2, F3, F4, F5, F6, F7, step 1.1]

3.1 Choosing a code, controlling the lift and setting the check interval are therefore linked design decisions in these models. The article's environmental-information explanation is an interpretation of that design picture, not a separate measurement asserted here. Actual platform performance and any outer-code overhead require the additional control, noise and resource specifications described in [F5] and [F7]. [F1, F2, F3, F4, F5, F6, F7, step 1.1] ∎