fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 116435–116528

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:55:10 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.
No candidate clears the applicable admissibility/evidence gates.Emit AbstainOutcome or EscalationOutcome, naming the blocking pins, basis and next use; an empty shortlist leaves the stop unexplained.

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):

    • This block activates exploration and exploitation-governed dispatch.
    • Post‑2015 examples that typically land here: modern bandit‑style or Bayesian selection under explicit risk budgets; adaptive evaluation and probing regimes; safe‑exploration variants where “abstain” or “degrade” is policy-bound.

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):

    • This block pins dispatch decisions to explicit rule and branch ids, enabling auditable “why” without inventing a fourth acceptance status.

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.
    • Post-2015 families that typically use this extension declaration: MAP-Elites-class QD including later archive-centric refinements, CMA-ME-class hybrids, modern illumination and coverage telemetry regimes where admissibility and edition pinning matter.

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.
    • Post‑2015 examples typically referenced via G.2 family cards: POET‑class and later open‑ended and co‑evolutionary regimes, including enhanced variants where transfer policies and validity gates must be edition‑pinned.