Correctness of first-order byte-sized posit dispatch #
The tagged selector agrees with the shared planner metadata, and every named execution branch implements the independent configured specification. These results ensure that removing closure dispatch changes performance only, never arithmetic semantics or inspection metadata.
Tagged selection uses the same candidate comparison as the shared metadata planner.
Agreement with the public certified portfolios #
Addition exposes exactly the metadata consumed by its first-order selector.
Subtraction exposes exactly the metadata consumed by its first-order selector.
Multiplication exposes exactly the metadata consumed by its first-order selector.
Division exposes exactly the metadata consumed by its first-order selector.
Square root exposes exactly the metadata consumed by its first-order selector.
FMA exposes exactly the metadata consumed by its first-order selector.
Executed and reported addition selection agree.
Executed and reported subtraction selection agree.
Executed and reported multiplication selection agree.
Executed and reported division selection agree.
Executed and reported square-root selection agree.
Executed and reported fused-multiply-add selection agree.
Arithmetic refinement #
A byte-addition choice cannot change arithmetic semantics.
First-order byte addition refines the configured specification for every policy.
A byte-subtraction choice cannot change arithmetic semantics.
First-order byte subtraction refines the configured specification for every policy.
A byte-multiplication choice cannot change arithmetic semantics.
First-order byte multiplication refines the configured specification for every policy.
A byte-division choice cannot change arithmetic semantics.
First-order byte division refines the configured specification for every policy.
A byte-square-root choice cannot change arithmetic semantics.
First-order byte square root refines the configured specification for every policy.
A byte-FMA choice cannot change arithmetic semantics.
First-order byte FMA refines the configured specification for every policy.
Function equalities used by capability construction #
Policy-selected byte addition equals the configured specification as a function.
Policy-selected byte subtraction equals the configured specification as a function.
Policy-selected byte multiplication equals the configured specification as a function.
Policy-selected byte division equals the configured specification as a function.
Policy-selected byte square root equals the configured specification as a function.
Policy-selected byte fused multiply-add equals the configured specification as a function.