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 22:54:38 UTC

G.5:4.4a - Worked selector slice

  • A catalyst-search team is choosing among three method families for the same declared TaskSignature and C.22.1 adaptation signature.

  • For each of the first two families the team tests a research setup using the member it would choose for each task. The setups start below the common threshold, with comparable prior exposure, the same check schedule and budget, and the same assistance available in testing and in the intended work. By the first scheduled check, the first setup passes and the second still falls short. The second passes at a later check. On the adjacent tasks the second setup performs better under the same test conditions.

  • The project values both passing the early check and performance on those adjacent tasks. Each of the two eligible alternatives has an established advantage on one of these criteria. The selector returns them as an unordered Shortlist and records the trade-off in the DRR and SCR. For the third family the evidence falls short of MinimalEvidence and the selector abstains. To credit the original training for performance on adjacent tasks, use the transfer comparison in C.22.1:8.

  • If the project also needs to identify the dated selection Work and its precise performer, A.13 first recovers CatalystSelectorSystem-17 : U.System for exact action CatalystFamilySelectionAction-17. CatalystSelectorBoundary-17 contains the deployed selector runtime, its effective policy state, and its registry/evidence interfaces; it excludes the method-family rows, TaskMap, result records, assignment, and containing team System. The action applies the effective selector to the three candidate families and returns the retained set. Its scope is CatalystFamilySelectionClaimScope-17, its working situation is CatalystSearchSelectionSituation-17, and its window is 2026-07-30T10:00:00Z through 2026-07-30T10:08:00Z. CatalystSelectionAdmissibilityNorm-17 directs the selector to exclude candidates that fail MinimalEvidence, preserve admissible non-dominated alternatives, and abstain rather than manufacture a scalar winner. Relevant conditions include the exact CatalystTaskSignature-17, current row and map editions, eligibility evidence, comparison policy, and adaptation-signature values.

  • A.2 declares local agential kind CatalystMethodSelectorSystemRole. Its membership criterion requires the stable work-facing contribution of method-family selection and goal-directed, condition-sensitive regulation under CatalystSelectionAdmissibilityNorm-17: the holder must apply the current gates, preserve the admissible set-return semantics, and abstain or escalate when no candidate qualifies. CatalystSelectorDecisionTrace-17 shows CatalystSelectorSystem-17 excluding the third family for failed MinimalEvidence, retaining the first two as non-dominated, and emitting no scalar winner. The trace and boundary/runtime records support the criterion facts under A.2’s membership rule; A.10 makes that source-to-use account recoverable. The case independently classifies CatalystSelectorSystem-17 under CatalystMethodSelectorSystemRole; neither the assignment nor the candidate Work supplies the classification. No Grade, autonomy result, characteristic profile, or stronger assurance claim is consumed.

  • The same A.13 core uses CatalystSelectorAssignment, a directly declared species under U.SystemRoleAssignment. The species declares holder, assigned-kind, and task-signature participant meanings and the assignment predicate. CatalystSelectorAssignment-17 obtains with CatalystSelectorSystem-17, CatalystMethodSelectorSystemRole, and CatalystTaskSignature-17 as its exact participant values; its maximal uninterrupted predicate-true interval covers the stated scope, situation, and window.

  • Only after that core is established does A.15.1 independently admit CatalystSelectionWork-17 : U.Work from the exact selection-action history, enacted CatalystFamilySelectionMethod, temporal extent, and obtaining containing-System relation to independently admitted CatalystSearchTeamSystem. Actual application CatalystSelectApplication-17 separately carries its effective candidate, criteria, and A.19 SelectionSlot bindings. Neither the assignment nor F.6 is an A.15.1 admission premise.

  • Because this account states that the Work was performed under CatalystSelectorAssignment-17, F.6 afterward establishes performedUnderAssignment(CatalystSelectionWork-17, CatalystSelectorAssignment-17) through that same obtaining A.13 assignment. The direct case fact links the exact pair, holder equality holds, and the assignment interval covers the Work. A different overlapping assignment held by the same System would not establish this attribution. A short result may omit the assignment identifier only after every fact consumed by the attribution remains recoverable.

  • A persisted shortlist assertion is a separate C.2.1 episteme; its DRR or SCR references do not by themselves prove the exclusion facts, warrant the result, authorize downstream action, or make that episteme available to an audience.

  • When one upstream C.19 pass has already narrowed the live pool to one internal retained subset over registered families, G.5-6 DeclareSetResult may declare that result as one Shortlist with one ShortlistId and explicit basis pins only when selector-facing result declaration is now the question. Until that declaration occurs, the internal retained subset is not yet one G.5 shortlist result.

  • When one upstream C.11 pass has already fixed one local choice over one declared source set, C.19 has fixed one retained pool treatment, an accepted decision has fixed all-member inclusion, or C.24 has produced one enactment-facing narrowed handoff, use G.5-6 DeclareSetResult when selector-facing set-result content is now the question. Until that declaration occurs, the ChoiceResult, PoolPolicyResult, accepted inclusion basis, CallPlan, or CheckpointReturn is not itself that G.5 result. A JointUseSet over non-Method members uses DeclareSetResult and does not pass through RegisterFamily or G.5-3 Select; ordinary generator selection retains the S1′/S3 branch.