33.36 turns ultra-long fiber corridors into a common-delay court: after multi-wavelength de-dispersion, round-trip asymmetry correction, and equipment-state masking, only a residual delay that stays zero-dispersion across wavelengths and directions, co-occurs at zero lag, tracks J_tension in a feed-forward monotonic or threshold-like way, and replicates across corridor families and operators can survive; under V08/V09-compatible tighten, this remains only a link–corridor–environment ledger, not a verdict on propagation ontology, crustal-tension ontology, or redshift/delay as a whole.
Use this section as a compact machine-readable EFT reference.
33.36 recasts ultra-long fiber routes from communications infrastructure into an engineering common-delay court. The key is not that the links are long, but whether multi-wavelength, bidirectional, multi-corridor residuals still carry one frequency-independent, zero-lag delay after standard stripping; under compat adjudication, the chapter is tighten.
The chapter compresses the case into five readouts: a segment-level common-delay index, zero-dispersion consistency, zero-lag co-occurrence, feed-forward hit rates against J_tension, and spatial stitching continuity across overlapping corridor segments. What matters is not one drifting link, but whether a common delay can be written as a corridor-level object that is wavelength- and direction-insensitive yet environment-predictable.
The workflow must run terrestrial, subsea, and mixed land–sea corridor families in parallel, while keeping shared timescale anchoring, dispersion and dispersion-slope removal, equipment and traffic masking, and corridor–environment overlay as separate ledgers. Feed-forward teams may only use J_tension and corridor masks, and measurement teams may not delete segments, swap de-dispersion kernels, or retune corridor partitions after unblinding.
False structure must be broken by wavelength-label, direction-label, segment-label, and time-window permutations, by time reversal and geometry-scramble nulls, and by complete equipment, traffic, and operator replication audits. Temperature chains, EDFA or ROADM state, PMD, traffic load, timestamp queues, and maintenance events are ordinary ledgers that must eat the pattern before any corridor common delay remains admissible.
The pass line is severe: across at least two link classes, two pipelines, and two operating teams, the residual delay must stay zero-dispersion across wavelengths and directions, co-occur at zero lag, and track J_tension in a monotonic or threshold-like way on preregistered holdout units. If ordinary link physics, equipment state, or traffic law explains the signal, or if it flips on holdouts, the chapter is falsified.
The chapter ends with only one link–corridor–environment ledger under the first-line path court, not a verdict on propagation ontology, crustal-tension ontology, or redshift/delay as a whole. If the common delay survives, it sharpens the engineering edge of V08-8.4 and V09-9.6; if not, it must return to link engineering and timebase ledgers before routing forward to 33.37.