ADR 0095: Bounded numeric variation

Context

The public contract permits target variation but does not provide a complete allowed-result set or discovery mechanism for each numeric variation point. Review must name the selecting profile or visible mode for every non-portable result, bound the allowed results, and require generic validation to reject an unknown profile or unconfigured implementation-defined rule.

ADR 0042 inventories all 99 domain/dimension variation points and assigns their current decision owner to pto-numeric-v1. The proposal under review permits no unbounded implementation-defined numeric result. A future delegation must name a profile or visible mode, enumerate or mathematically bound allowed results, and provide discovery metadata. Generic validation rejects unknown profiles, unknown modes, and missing rules before effects.

Affected domains

• cube-matrix
• scalar-binary
• scalar-fp-convert
• scalar-fp-to-integer
• scalar-fused
• scalar-integer-to-fp
• scalar-unary
• tile-binary
• tile-compare
• tile-convert
• tile-dequantize
• tile-expand
• tile-fused
• tile-order
• tile-partial
• tile-quantize
• tile-reduction
• tile-unary

Alternatives considered

• named target-profile rules;
• implementation-defined rules with explicit allowed sets; and
• unsupported-in-profile dispositions.

Blockers

• Select one admissible route for every non-portable variation point.
• Populate a bounded allowed-result contract for every selected delegation.
• Add unknown-profile, unknown-mode, and missing-rule rejection vectors.

Acceptance obligations

• A profile discovery and selection contract.
• Allowed-result sets for every implementation-defined rule.
• Unknown-profile and missing-rule rejection tests.

Decision

No variation route or numeric result is accepted by this draft.