The transpose ledger: the explicit two-path transform factor #
The two-path separated move transforms the
constrained summand by an explicit factor T. This file pins
T down, for the separated orientation class over the transported
orientation:
T = twoPathTransformFactor = −1,
independent of the boundary state, of the ∂-data at the four
re-paired ends, and of the transition system beyond the two-chain
separated configuration. The decomposition behind the constant:
- the vertex bookkeeping contributes the alternating-evaluation
transposition sign of the two re-paired pair-blocks at the
square's vertex (
MixedFunctional.evalOdd_transpose, the engine insidethroughSummand_transportRepair):−1; - the
oddPartnerSignfactors at the two changed blocks merely commute (+1); - the colour re-routing between the two chains is, at the sum
level, the identity reindexing of the
φ-sum: the transported orientation keepsisOut, each repaired chain still carries its boundary colour data along the same strand segments, and only the partner entries of the two vertex blocks swap. So the state-dependent piece is+1for every boundary state — the colour sets the functional is evaluated on change, but the colourings themselves are not re-indexed.
Main results #
EdgeSubset.twoPathTransformFactor— the explicit factor,(-1 : ℂ)(twoPathTransformFactor_eq_neg_one).EdgeSubset.twoPath_transform— the two-path transform: on a two-chain (non-localized) separated square,throughSummand (transportRepair o) (count κ') = T * throughSummand o (count κ)(count invarianceopenCircuitCount_repair_of_not_localizedplus the vertex ledgerthroughSummand_transportRepair);twoPath_transform_expis the fixed-exponent form, showingTis exponent-independent.TransposeVerify— a worked instance carrying the vocabulary concretely, and the valuecSummand_O = −1thatThroughIndCFalse.leancompares against.
The two-path transform factor: the explicit T of the
separated two-path move over the transported orientation. It is
the transposition sign of the alternating evaluation at the
square's vertex; the oddPartnerSign commutation and the colour
re-routing contribute +1 each, so T is constant — independent
of the boundary state, the ∂-data at the four re-paired ends,
and the transition system.
Equations
Instances For
The factor unfolded.
The fixed-exponent transform: at every circuit exponent the
transported summand is T times the old summand — T is
exponent-independent (restating the vertex ledger with
the explicit factor).
The two-path transform: a repair at a two-chain square
(twoChains_of_not_localized configuration), separated class, over
the transported orientation, transforms the constrained summand at
the open circuit counts by the explicit factor
T = twoPathTransformFactor = −1 — the circuit count is unchanged
and the vertex transposition supplies the sign; the state-dependent
∂-piece of the colour re-routing is trivial at the sum level.
The worked instance #
One vertex carrying two boundary-to-boundary paths with disjoint
boundary chords: labels 0 < 1 < 2 < 3, chain (0,1) through the
matched pair 0 ↔ 1, chain (2,3) through 2 ↔ 3 (flags 0–3
internal, flags 4–7 at the boundary labels), edge assignment
pairing = ![4,5,7,6,0,1,3,2]. The square 0 ↔ 1, 2 ↔ 3 is
non-localized, the orientation ![F,T,T,F] is separated
(isOut 2 = !isOut 0), both circuit counts are 0, and both
chord-crossing counts are 0, so both path signs are trivial
(cChord_kappa, cPathSign_kappa).
Against the functional supported on the colour set {0,5,2,7} the
constrained summand is −1 (cSummand_O). LoopVerify.lean
computes the same summand for a repaired system at a flipped
orientation, and ThroughIndCFalse.lean reads the two values off
to refute independence across boundary pairings.
One vertex, four pendant edges: flags 0–3 at the vertex,
flags 4–7 at boundary labels 0–3; edges {0,4}, {1,5},
{3,6}, {2,7}.
Equations
- One or more equations did not get rendered due to their size.
Instances For
The unique vertex.
Equations
Instances For
The full edge subset.
Equations
- RS.TransposeVerify.cSubset = { flags := Finset.univ, pairing_mem := RS.TransposeVerify.cSubset._proof_1 }
Instances For
The matching 0 ↔ 1, 2 ↔ 3: two boundary chains with
disjoint chords (0,1) and (2,3).
Equations
- RS.TransposeVerify.cKappa = { match_ := RS.TransposeVerify.cMatch, match_invol := ⋯, match_ne := ⋯, match_mem := ⋯, match_vertex := ⋯ }
Instances For
The square 0 ↔ 1, 2 ↔ 3 at the vertex.
The separated, path-canonical orientation: both chains enter the vertex through their low-label ends.
Equations
Instances For
The boundary state: odd colours 0, 1, 2, 3 at labels
0, 1, 2, 3.
Instances For
The state matches the fragment's boundary: each of the four legs carries the colour the state names.
The functional supported on the colour set {0, 5, 2, 7} (the
odd-list set of the original summand).
Instances For
The pinned core colouring #
Every flag is a core flag.
No flag is a through flag: both boundary chains pass through the vertex.
With no through flags the through product is 1, so it drops
out of both summands being compared.
The pinned core odd colouring.
Equations
- RS.TransposeVerify.cPhi = ⟨fun (g : ↥RS.TransposeVerify.cSubset.coreFlags) => RS.TransposeVerify.cColour ↑g, ⋯⟩
Instances For
The unique (empty) even colouring.
Equations
Instances For
The even colouring is unique: there is nothing to choose.
The empty even colouring matches the state's even part: with
k = 0 there is nothing to check.
The pinned colouring is boundary-matched.
The colouring is forced: every boundary-matched core odd colouring is the pinned one, so each summand is a single term.
Two-element in-lists #
The in-flag list at the vertex, up to order, read off an
orientation's isOut table: the two flags oriented inwards.
The summand over a two-element in-list #
The vertex sign over a two-element in-list: the product of the
two entry partners' oddPartnerSigns.
The vertex odd list over a two-element in-list: each in-flag's colour followed by its match's partner colour.
The summand over a two-element in-list: with the colouring forced and the through product trivial, the whole summand is the single vertex factor.
Open circuit counts #
No system on this instance has periodic flags: every flag lies on a boundary-to-boundary chain.
Pointwise form of cPeriodic_empty.
Every system on this instance has open circuit count 0, so
the original and repaired summands are compared at the same loop
weight.
Path matchings and chord-crossing counts #
Path-match evaluation along a one-internal-step chain: enter at
β, cross to x, match, leave at g.
The original system's chain from 4 ends at 5.
The original system's chain from 5 ends at 4.
The original system's chain from 6 ends at 7.
The original system's chain from 7 ends at 6.
Reading a chord's two labels off a chain: the labels recorded
by attach at the chain's ends are the chord's.
A system whose chords all join adjacent labels has no
interleaving pair, hence crossing count 0.
The original system's chords (0,1) and (2,3) are disjoint:
crossing count 0.
The repaired system's chords (0,3) and (1,2) nest:
crossing count 0 as well.
The original path sign is 1.
The repaired path sign is 1 too — so the factor the two
summands differ by is not the chord sign.
The two summand values #
The original summand is −1.