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:40:20 UTC

G.5:4.4d - Worked result-declaration closure slice

Receiving situationComplete result and changed action
The two pump Methods in §0.5 survive, with no admitted ordering.Emit its unordered Shortlist; the receiver still has a choice to make.
A declared comparator orders family_B before family_A for the specialist handoff.Emit a RankedShortlist with [family_B, family_A], the comparator and supporting basis pins, and the handoff use. A request for an order alone supplies no comparator.
The cohort decision includes FPF@C, Domain@D and Local@L together.Emit the §4.4b JointUseSet; the receiver uses all three exact editions under the inclusion conditions.
Required selection grounds are missing, or the established gates exclude every candidate.Emit AbstainOutcome with the respective unknown or failed condition and its basis. Use EscalationOutcome only for a justified further inquiry or action. If an admitted Select application instead returns an empty set under its declared criteria, preserve that actual result and explain its scope.

The following extensions apply only when their corresponding mode is active. Their declared Uses and pins cite the governing semantics.

GPatternExtension block: G.5:Ext.EELog

  • PatternScopeId: G.5:Ext.EELog

  • GPatternExtensionId: EELog

  • GPatternExtensionKind: MethodSpecific

  • GoverningPatternId: C.19

  • Uses: {C.19}

  • ⊑ and ⊑⁺: ∅

  • Required pins, edition pins, and policy pins (minimum):

    • EELensPolicyRef (or equivalent lens or policy id carried by C.19)
    • RiskBudgetRef?
    • ProbeAccountingRef?
    • FailureBehaviorPolicyId? (if degrade behavior is governed by policy)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.FreshnessOrDecayEvent}

  • Notes (extension discipline; semantics cited):

    • Use this block for dispatch under an exploration and exploitation policy.
    • Examples include bandit-style or Bayesian selection under explicit risk budgets, adaptive probing, and exploration with policy-bound abstain or degrade behavior.

GPatternExtension block: G.5:Ext.SoSLOG

  • PatternScopeId: G.5:Ext.SoSLOG

  • GPatternExtensionId: SoSLOG

  • GPatternExtensionKind: MethodSpecific

  • GoverningPatternId: C.23

  • Uses: {C.23}

  • ⊑ and ⊑⁺: ∅

  • Required pins, edition pins, and policy pins (minimum):

    • SoSLogRuleId[]
    • SoSLogBranchId[] (including escalation branches, if used)
    • FailureBehaviorPolicyId (if degrade behavior is made explicit)
    • MaturityRungId[]? (when maturity ladders are used as gates; semantics come from C.23)
    • AdmissibilityLedgerRef? (when selector consumes admissibility rows rather than recomputing thresholds)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.MaturityRungChange, RSCRTriggerKindId.EvidenceSurfaceEdit}

  • Notes (extension discipline; semantics cited):

    • The pinned ids identify the rule and branch that governed each dispatch decision. Using a branch leaves the three acceptance statuses unchanged.

GPatternExtension block: G.5:Ext.NQD

  • PatternScopeId: G.5:Ext.NQD

  • GPatternExtensionId: NQD

  • GPatternExtensionKind: MethodSpecific

  • GoverningPatternId: C.18

  • Uses: {C.18, C.19}

  • ⊑ and ⊑⁺: ∅

  • Required pins, edition pins, and policy pins (minimum):

    • DescriptorMapRef.edition
    • DistanceDefRef.edition
    • InsertionPolicyRef
    • TaskSignatureRef (when QD is enabled via TaskSignature flags or traits)
    • active fields from C.21’s DHC replay basis (only when this telemetry consumes a C.21 DHC coordinate; carry exactly the fields that coordinate used)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.FreshnessOrDecayEvent}

  • Notes (extension discipline; semantics cited):

    • G.5 core remains QD‑agnostic; QD semantics are governed by C.18.
    • Examples include MAP-Elites-class QD, CMA-ME-class hybrids, and illumination or coverage telemetry whose descriptor and archive policies affect replay.

GPatternExtension block: G.5:Ext.OpenEndedFamilyWiring

  • PatternScopeId: G.5:Ext.OpenEndedFamilyWiring

  • GPatternExtensionId: OpenEndedFamilyWiring

  • GPatternExtensionKind: GeneratorSpecific

  • GoverningPatternId: G.2

  • Uses: {G.2, C.19, C.23}

  • ⊑ and ⊑⁺: ∅

  • Required pins, edition pins, and policy pins (minimum):

    • GeneratorFamilyRowRef[]
    • TransferRulesRef.edition (mandatory when Open‑Ended is enabled)
    • EnvironmentValidityRegionRef?
    • CoEvoCouplerRef[]?
    • SoSLogBranchId[]? (when validity of generated tasks is gated by explicit branches)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.FreshnessOrDecayEvent}

  • Notes (extension discipline; semantics cited):

    • This block enables declared sets of {Environment, MethodFamily} pairs without redefining generator semantics in G.5.
    • Examples referenced through G.2 family cards include POET-class and other open-ended or co-evolutionary regimes whose transfer policies and validity gates must be edition-pinned.