Configured total-order refinement #
Packing and decoding preserve both predicates exactly. Order laws and numerical, zero, and NaN rules are transported from the descriptor model, independently of the chosen runtime carrier. Mutual magnitude comparison identifies absolute exact values, including NaN metadata; opposite signs can tie.
Configured total ordering is exactly the descriptor-model predicate.
Configured magnitude ordering is exactly the descriptor-model predicate.
The configured predicate uses the shared complete exact-value order.
The configured magnitude predicate uses the shared exact magnitude order.
Packing two models preserves their total-order comparison.
Packing two models preserves their magnitude comparison.
Every configured datum precedes itself, including signaling NaNs.
Configured total ordering compares every pair of values.
Configured total ordering is transitive.
Mutual total ordering identifies the configured value, including its complete encoding.
Mutual total comparison is equivalent to equality for every configured storage plan.
Strict model numerical comparison is respected by configured total order.
Reversed strict numerical comparison fails configured total order.
Configured zero ordering depends only on the stored sign flags.
The configured NaN rule preserves sign, signaling class, and full fraction payload.
Magnitude comparison is reflexive on every configured value.
Magnitude comparison is total on configured values, including NaNs.
Configured magnitude comparison is transitive.
Mutual configured magnitude comparison identifies absolute exact data.
In a signed-zero format, magnitude ordering agrees with model absolute-value ordering.
All configured zeros tie under magnitude comparison.
Configured NaN magnitudes compare signaling class, then increasing fraction payload.