The de-isolation flow is the wing-factorised flow #
Category: 3-Local (CV; the instantiation BACKLOG #139 was left owing). BACKLOG #139, second half; closes #131's two-dynamics gap.
TwoWingFactorisation.lean proved the cone for any wing-factorised
flow and instantiated it at CompositeArena's leftOp/rightOp. What it did not do was plug in
LF6.localFlowUnitary itself — the index alignment was checked by hand and left as a claim about
conventions. This file formalises it, so "the cone comes from the measurement interaction" stops
being a reading of two index conventions and becomes a theorem.
The alignment, written out #
LF6.jointFlowEquiv is jointDilEquiv.trans finProdFinEquiv, and jointDilEquiv's source is
(sys_A ⊗ ptr_A) ⊗ (sys_B ⊗ ptr_B) — per wing. So localFlowUnitary is a per-wing Kronecker
product U_A ⊗ U_B wearing a Fin (4 * 4) label. On the CV side FieldConfig 4 2 = Fin 4 → Fin 2
is four two-level modes. The identification is three steps, each already in the corpus:
wingIndexEquiv—FieldConfig 2 2 ≃ Fin 2 × Fin 2(piFinTwoEquiv): a two-mode configuration is a (system, pointer) pair;wingSplitEquiv—FieldConfig 4 2 ≃ (Fin 2 × Fin 2) × (Fin 2 × Fin 2), which isCompositeArena.configSplitfollowed by that, per wing;configFlowEquiv— the whole way across toFin (4 * 4), by composing withjointFlowEquiv.
Then:
- ★★★
reindex_localFlowUnitary_eq_joinU— the de-isolation flow, read on the four-mode configuration space, is exactlyCompositeArena's product unitaryjoinU wingU wingU. ThejointFlowEquivcancels against its own inverse, and what is left is the Kronecker product read throughconfigSplit— which is whatcompositeReindexis; - ★★★
joinU_wingU_eq_mul— and that product is the product of its two wing factors, so it satisfies the hypothesis ofTwoWingFactorisation's theorems; - ★★★
arenaObs_kick_deisolationand ★★★recordStroke_comm_kick_deisolation— a B-wing intervention cannot steer A's reading or A's record write, at every power of the de-isolation flow. No graph, no period count, and no second interaction: the cone is the measurement's own.
What this closes, and what it does not #
#131's two-dynamics gap closes. Causal separation and the Born/record/CHSH statements are now
about the same interaction: localFlowUnitary, up to the index relabelling written out above. The
experiment no longer takes its causal structure from one dynamics and its statistics from another.
⚠️ Locality is still assumed, just once and physically. localDeisolation_factorises holds by
construction — LF6-A.3 chose a product dilation — so what is derived is "the cone follows from the
product form", not "the product form follows from anything". Deriving that is R-016, untouched.
⚠️ One thread remains, and it is about the projective action, not about which dynamics. These
statements are about arenaKick of the pulled-back unitary on FieldArena 4 2;
LF6.localDeisolationFlow is localFlowUnitary • · on CPN (4 * 4). Those agree up to
ArenaIndexBridge.lean's arenaEquiv, and the identity
arenaKick (pullback) = arenaEquiv.symm ∘ localDeisolationFlow ∘ arenaEquiv is not proved here.
It is bookkeeping about a projective action, with no choice left in it, and it is what a capstone
would need; it is recorded on #139 rather than claimed.
⚠️ Static, not propagating — inherited from TwoWingFactorisation: a product unitary gives
disjoint-support commutation, not a velocity. TwoWingCone.lean keeps the graded
version for a coupled dynamics.
References: TwoWingFactorisation.lean
(supportedOn_heisenberg_pow_of_factorised, arenaObs_kick_of_factorised,
recordStroke_comm_kick_of_factorised, leftModes_two_two),
CompositeArena.lean (configSplit, compositeReindex, joinU, leftU,
rightU, leftOp_mul_rightOp, leftOp_supportedOn),
TwoWingCone.lean (wingAModes, wingBModes),
LF6/LocalDeisolationFlow.lean (localFlowUnitary, jointFlowEquiv, jointDilEquiv,
localDeisolation_factorises), LF5's vnUnitary;
specs/BACKLOG.md #139, #131, R-016.
The alignment #
A two-mode configuration is a (system, pointer) pair.
Equations
- CSD.CV.wingIndexEquiv = piFinTwoEquiv fun (a : Fin 2) => Fin 2
Instances For
The four-mode configuration space, split per wing into the de-isolation's own index: modes
0,1 are A's (system, pointer) and modes 2,3 are B's.
Equations
Instances For
All the way across, to the Fin (4 * 4) label LF6 works in.
Instances For
A per-wing unitary, read on a two-mode configuration space.
Equations
Instances For
The de-isolation flow is the product unitary #
★★★ The de-isolation flow, read on the four-mode configuration space, IS
CompositeArena's product unitary. The jointFlowEquiv cancels against its own inverse and what
is left is the per-wing Kronecker product read through configSplit — which is exactly what
compositeReindex does. So the measurement interaction and the composite arena's product dynamics
are the same matrix.
The two wing factors #
The A-wing factor of the de-isolation flow, as a unitary on the four-mode space.
(CompositeArena packages rightU but not its mirror, so both are spelled out here.)
Equations
Instances For
The B-wing factor.
Equations
Instances For
★★★ A product unitary is the product of its two wing factors, so the de-isolation flow meets
the hypothesis of TwoWingFactorisation's theorems.
★★ The flow the next two theorems are about is the de-isolation flow, read on the four-mode configuration space.
The cone, for the de-isolation flow itself #
★★★ A B-wing intervention cannot steer A's reading, at every power of the de-isolation flow. The cone is the measurement interaction's own: no coupling graph is supplied and no period budget is tracked, because the interaction does not couple the wings at all.
★★★ And it cannot steer A's record write. This is #131's causal-separation property with its causal structure read off the measurement, which closes that row's two-dynamics gap.
The arena identification intertwines the two actions #
The theorems above are about arenaKick of the pulled-back unitary on FieldArena 4 2, while
LF6.localDeisolationFlow acts on CPN (4 * 4). This section closes that last thread: the aligned
arena identification carries one to the other, so the CV statements and the LF6 statements are
about the same map and not merely the same space.
The identification of the state spaces, aligned with the de-isolation's own wing split. (Not
ArenaIndexBridge's fieldSpaceEquiv, whose index change is an arbitrary
Fintype.equivFinOfCardEq and therefore carries no wing structure.)
Equations
Instances For
The aligned arena identification: the CV field arena and the projective space LF6 works
in, identified so that the wing split is respected.
Instances For
★★ The pulled-back unitary acts as the de-isolation unitary, through the identification.
A coordinate computation: reindexing the matrix and reindexing the vector cancel, the sum being
reindexed by configFlowEquiv.
★★★ The identification intertwines the CV kick with the de-isolation flow. So every
statement proved above about arenaKick (wingLeftU * wingRightU) is a statement about
LF6.localDeisolationFlow, transported — the CV cone and the LF6 Born/record/CHSH statements are
about the same map, not merely the same space.
This is the last thread #131 was carrying.