Finite chronological ancestry and blossom compilation #
A single backwards scan reconstructs actual root paths. Timestamps are paid for by the older log's length and retain copied-constraint identity. Original names and public occurrence positions remain binary. The representation bookkeeping is original; the two LCA cases are those of [KKR18], arXiv:1602.03124v6, Section 5.3, printed pp. 11–12.
Backwards-scan state: queried binary variable and the already reconstructed suffix.
- start : ℕ
Current ancestor's binary original name.
Actual binary global port pairs in root-to-leaf order.
Actual copy timestamps, in the same order and encoded unary.
Instances For
Follow one actual parent through a strictly older expansion.
Instances For
Scan newest-first expansions with the actual decreasing copy timestamps.
Instances For
Root-to-variable ancestry with exact ordered step positions and actual copy times.
Instances For
Forget only the copy timestamps of an actual ancestry code.
Instances For
Actual variable/copy node codes; copied nodes keep original constraint and time.
Instances For
Original variables alternate with actual timestamped copied constraints.
Instances For
The full common root-path prefix, retaining both coordinates of a copied constraint.
Instances For
The preparatory root path and actual closed cycle; metadata remain in the source layer.
- prepare : EdgeAugmenting.WalkCode
Root-to-base path whose flip prepares the blossom.
- cycle : EdgeAugmenting.WalkCode
Actual cycle in original global port order.
Instances For
The preparation walk is framed, followed by the cycle walk.
Instances For
The tuple of the fields of encBlossomCode.
Instances For
Append two actual walks, preserving the first one's original start.
Instances For
Candidate augmentation: the left ancestry, meeting pair, and reversed right ancestry.
Instances For
Both actual LCA cases, including the final child-to-child pair for a copied-constraint LCA. Every scope lookup and prefix length is bounded by an actual list.
Instances For
A single native backwards scan has exactly the source's chronological ancestry. No forest invariant, validity, width or edge-instance premise is needed for this bridge.
The native ancestry compiler constructs the exact original augmenting walk.
The native compiler retains the exact preparation and cycle of both source LCA cases.
The metadata and mathematical invariant remain the existing Meeting.blossomData API.