Synchronizing two epsilon introductions #
Two epsilon rules which introduce the same characteristic list child have the same productive future. This file isolates the counted synchronization argument from the remaining structural ancestry argument: equal global positions force the two source heads to be literally equal, even though the terminal suffixes following the child may differ.
A leftmost structural trace from a list position to a single position
may move the entire hidden context into the displayed list at its source.
The trace cannot be reflexive, and its first event is necessarily split;
after that event both source decompositions reach the identical single
position.
Converging epsilon exits also synchronize when their two structural
traces start from different displayed/hidden decompositions of the same
physical list cut. Expanding both source contexts into their displayed
lists gives a literal common LeftmostEpsilonPosition, after which the
general converging-trace theorem applies.
A zero-visible tail starting at a single node retains the complete
hidden context of that node. This is the non-anchor variant needed when one
epsilon parent is assumed to be a structural descendant of the other.
Equal-length globally rooted realizations of two concrete epsilon introductions of the same list child have the same source state and exposed stack symbol.
The common completion of the child supplies usefulness on both sides. The one-symbol hypothesis is needed only when that completion is empty.
If the second epsilon parent is a zero-visible structural descendant of the first, the two exposed heads are equal. A genuinely nonempty descendant tail retains the first hidden context. Its first PDA step synchronizes with the direct epsilon edge to the common child; the remaining retained segment therefore repeats that child cut, either exactly or with a nonempty inserted stack block. Both alternatives contradict usefulness.
Symmetric interface: structural zero-visible comparability of the two parent occurrences is sufficient for epsilon/epsilon head uniqueness.
Two concrete epsilon introductions whose last-visible anchors denote the
same physical position have equal source heads. The anchors may retain
different grammar target indices: LeftmostEpsilonPosition deliberately
forgets those indices and synchronizes the productive zero-visible traces
at the operational cut.
Two concrete epsilon introductions also synchronize when their selected last-visible anchors are list nodes with the same physical PDA cut. The displayed lists and hidden contexts need not agree separately: equality of their concatenations is exactly the information supplied by equality of two split-return endpoint configurations.
The last structural residual for two epsilon introductions of one list
child. Both concrete parents and their zero-visible ancestries are retained.
The paired anchors have unequal physical positions; paired root and read
anchors therefore cannot inhabit this datum, so its paired witness is
necessarily a splitRight/splitRight pair.
Keeping the position inequality, rather than flattening the split constructor into a large tuple, preserves the two original structural spines for the interval argument which consumes this residual.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Concrete epsilon introductions either synchronize at their paired
last-visible anchor, or expose the exact unequal-position paired-split
residual. Root and read pairs have equal physical anchor positions, so the
right disjunct can only survive the splitRight constructor of
PairedVisibleAnchors.
Active-spine interface for the same classifier. A single completion of the shared child prefix is chosen first, so both returned concrete parent spines live over the same completed word.
The exact unequal-position residual for two epsilon introductions. It retains the normalized parent spines and their globally counted source cuts; no interval or hidden context has been compressed away.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Active epsilon introductions either already have equal source heads, or expose the exact unequal-count structural datum needed by the frontier-trace comparison argument.
Operational orientation of the unequal-count residual. Besides the positive epsilon-only segment between the two parent cuts, the conclusion retains a common completion of the shared child and both useful child endpoints. These are the exact ingredients needed to rule out a purported structural extension by the useful-cycle and stack-growth kernels.