Wiring the geometric phase evaluator #
The generated point block precedes the original input. Constant validity flags discard the zero scalar. Each request payload carries both its original data and the complete generated point list of that candidate, so accepted point lists can become occupancy inputs in the next phase.
Total width of the generated point block.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Constant scalar-validity flags for every menu point.
Equations
- One or more equations did not get rendered due to their size.
Instances For
The point address of a generated record.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Carry original request data followed by all candidate-specific point bits.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Padded validity is preserved at the corresponding triple index.
Generated point keys have the exact field-level affine-line semantics.
The set tested by the menu evaluator is precisely the encoded punctured line.
Original request data is carried without modification.
The point-list suffix of a request payload carries the generated keys.
Lifting source wires past preprocessing preserves their occupied set.
The evaluator's encoded cleanliness predicate is exactly geometric cleanliness.