Canonical ordering by preserved routing metadata #
After gather matching, destination records must be ordered by their preserved
(request, line position) metadata rather than by the (group, point) key
used for matching. This module constructs the free within-record
permutation selecting (tag, metadata) as the second sort key, preceded by
the same explicit tag-complement pass used for scatter.
Forward block swap taking virtual (tag, metadata, matching key, value)
positions to physical (matching key, tag, metadata, value) positions.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Inverse physical-to-virtual block swap.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Permutation swapping the matching-key and (tag, metadata) blocks while
leaving the copied-value block fixed.
Equations
- One or more equations did not get rendered due to their size.
Instances For
A virtual (tag, metadata) bit maps to the corresponding physical bit
after the matching-key block.
The selected virtual prefix is exactly the complemented physical tag followed by the preserved metadata field.
Flip tags and canonically order complete records by (tag, metadata).
Equations
- One or more equations did not get rendered due to their size.
Instances For
Explicit tag-flip and metadata-ordering circuit.
Equations
- One or more equations did not get rendered due to their size.
Instances For
The exact gate count of canonicalSortCircuit.
Complete gather-match and canonical-order pipeline #
Canonical (tag, metadata) header of a standalone record.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Metadata header after complementing the record tag.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Semantic gather match followed by canonical metadata ordering.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Explicit two-sort gather circuit.
Equations
- One or more equations did not get rendered due to their size.
Instances For
The exact gate count of matchedCanonicalRoutingCircuit.
The complete metadata-routing pipeline permutes complemented initial
(tag, metadata) headers.
Canonical rank of destination metadata #
Destination metadata at one canonical prefix position.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Exactly target.val initial records have complemented order metadata
strictly below the target destination's canonical metadata.
Flattening and exact-capacity casting preserve the destination metadata rank count.
Unique canonical destination headers #
The canonical metadata header for one destination occurs exactly once in the semantic routing layout. Matching keys need not be injective here: the preserved destination-order metadata supplies the uniqueness.
Exact-capacity casting and flattening retain the unique canonical destination metadata header.
Fixed output positions #
After matching by the runtime key and sorting by preserved destination
metadata, destination target occupies literal output record target.
The value copied into destination target also occupies its literal
canonical output record. This is the generic fixed-wire correctness theorem
used by the gather pass.