Marker-loop cuts of compatible pseudocore splits #
Each marker introduced by loop splitting is joined only to its designated base vertex, by two parallel slot occurrences. The two vertices therefore form a canonical genus-one side of a core vertex cut.
Nonloop incidence degree at a pseudocore vertex.
Equations
- Utilities.Certificate.PseudocoreMarkerCut.nonloopValence core vertex = ∑ neighbor : Fin n, core.multiplicity vertex neighbor
Instances For
The incidence degree of an original vertex in a compatible loopless split core is its loop-aware pseudocore valence.
A displayed marker certifies a positive semantic-loop multiplicity at its base vertex.
If the pseudocore has only one semantic loop in total, every displayed marker is based at a vertex carrying exactly that one loop.
Stability forces the base of a unique semantic loop to have at least one nonloop exit.
The exact single-loop structural dichotomy: its base has one nonloop incidence (the separating-bridge case), or at least two (the wedge case).
The canonical two-vertex cut side for one split-loop marker.
Equations
- Utilities.Certificate.PseudocoreMarkerCut.cut split marker = { glue := core.baseVertex (split.markerBase marker), left := {core.baseVertex (split.markerBase marker), core.markerVertex marker} }
Instances For
Base and marker vertices lie in the two disjoint summands of the split core's vertex type.
The marker side is a rigid genus-one left factor whenever the split core is connected.
A connected subdivision presentation supplies the split-core
connectedness needed by the canonical marker rigidity theorem. This is the
form produced directly by pseudocorePresentation_genusFive.
Distinct loop-marker sides are nested in the expected way: after cutting off one marker cycle, the entire two-vertex side of any other marker remains in the complementary factor. The two marker cycles may share their base vertex; that common vertex is precisely the first cut's glue.