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

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:05:20 UTC

G.5:4.4b - Declared selected-set result and closure rule

State the selector-facing outcome and the information its kind requires, so the recipient can use it without reconstructing it from a selector trace, comparison note, or local choice.

For method- or generator-family dispatch, that result closes selector work over grounded rows. For a JointUseSet, it records already identified members that are all included for one named use. It does not replace registry maintenance, comparison rules, the upstream choice or inclusion basis, or the patterns that identify the members and their relations.

The admissible selector outcome families here are:

  • SelectorOutcomeKind = SetResultOutcome, whose closed SetResultFamily value set is Shortlist when alternatives are retained for later choice and the result does not order them, RankedShortlist when the result orders those retained alternatives, and JointUseSet when every named member is included for one named use;
  • SelectorOutcomeKind = HandoffOutcome, with HandoffKind = SpecialistHandoff or one other narrowed handoff plan when heterogeneity is the truthful downstream result;
  • SelectorOutcomeKind = AbstainOutcome when required grounds are missing or no candidate is admissible and selection cannot proceed; and
  • SelectorOutcomeKind = EscalationOutcome when a blocked selection warrants a specified further inquiry, decision or action by another competent receiver.

G.5-3 Select uses grounded candidates and the applicable eligibility/comparison basis. An admitted Select may return an empty candidate set under its declared criteria; a corresponding empty Shortlist retains that actual return, criteria and scope. An abstention instead records the failed or unknown condition and has no Select result binding. G.5-6 DeclareSetResult emits SetResultOutcome from exact already identified members and a current inclusion basis; it does not perform that upstream choice.

A JointUseSet uses this bounded representation:

  • namedUse states the one joint use;
  • memberEntries contains one keyed entry per included member;
  • every entry has one exact memberRef; the membership result adds no per-member contribution or basis field;
  • each exact memberRef occurs at most once, and entry order has no semantic effect;
  • if a serialization also emits top-level members, it is only the unique set projection of memberRef values from memberEntries, never a second maintained list;
  • ordering, inclusion conditions, and sufficient top-level basisPins remain explicit; and
  • candidate-pool membership and excluded candidates stay separate from emitted joint-use membership.

Exact content, claims about a member’s use or contribution, and direct relations keep their own governed records. When one supports the membership result, cite that existing record among basisPins; memberEntries creates neither the cited content nor a new contribution relation.

For framework use, memberRef may name an exact already identified edition under its existing identity rules. Do not populate MethodRef, create a registry row, or classify that edition as a Method merely to emit the result.

Every outcome states its SelectorOutcomeKind, public result kind when applicable, members, keyed entries, handoff content, or blocking condition, ordering, and sufficient basis pins. A handoff also states its next downstream use boundary.

A compact retained-alternative result may look like:

SelectorOutcome(
  selectorOutcomeKind = SetResultOutcome,
  setResultFamily = Shortlist,
  members = [family_A, family_C],
  shortlistId = shortlist_17,
  ordering = unordered,
  basisPins = [pathSlice_41, scr_22],
  nextUse = downstream_comparison
)

A compact joint-use result may look like:

SelectorOutcome(
  selectorOutcomeKind = SetResultOutcome,
  setResultFamily = JointUseSet,
  namedUse = cohort_review,
  memberEntries = [
    { memberRef = FPF@C },
    { memberRef = Domain@D },
    { memberRef = Local@L }
  ],
  ordering = unordered,
  inclusionConditions = [all_three_editions_required_for_cohort_review],
  basisPins = [choice_result_12, edition_basis_7]
)

Close with Shortlist or RankedShortlist when the result retains alternatives. Close with JointUseSet only when every member is included for the named use and that membership is established for every entry key. Close with a handoff, abstain, or escalation outcome when that is the actual result. A complete G.5 result states its basis and ordering status and supplies the fields its kind requires. For a set, these include its family, retained members or keyed joint-use entries, and the named use for joint inclusion. For a handoff, abstention or escalation, give the corresponding handoff content or blocking condition.