Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:30:10 UTC

G.5:10 - Rationale

  • Why registries? Stable row editions preserve the grouping and eligibility basis for later dispatch. Assurance records enter when required by the declared use or public-registration contract.
  • Why separation via Extensions? QD, OEE and preference-learning have different method semantics. Extensions let a selector use those semantics only for the task that needs them.
  • Why set-return? Partial orders are common and often the only admissible representation under heterogeneous scales; set-return preserves semantics and makes tie criteria explicit.
  • Why explicit defaults with one declared source? Indexing each default by its governing definition lets consumers use and revise the same rule.
  • Why selected-set result declaration here? Once the current question is to state retained alternatives or an all-member result for downstream use, the selector should declare that result directly instead of leaving it implicit in local choice, pool-policy, or enactment notes written for other purposes.
  • Why JointUseSet? A shortlist preserves alternatives for later choice; an all-member result says that removing one member changes the result for the named use. JointUseSet is a local SetResultFamily value using the existing member identities. G.5-3 Select may emit it only over exact Method candidates admitted through that kernel. G.5-6 DeclareSetResult covers already identified members with a current inclusion basis, including framework editions, without retyping them as Methods or asserting a relation among them.