Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

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:15:10 UTC

G.8:5 - Extensions (pattern‑scoped; non‑core)

G.8 keeps method/generator specificity out of the core kit. Any such specificity appears as GPatternExtension blocks with stable PatternScopeIds.

G.8:5.1 - G.8:Ext.SoSLOGWiring

PatternScopeId: G.8:Ext.SoSLOGWiring GPatternExtensionId: SoSLOGWiring GPatternExtensionKind: MethodSpecific GoverningPatternId: C.23 Uses: {C.23} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • SoSLogRuleId[]
  • SoSLogBranchId[]?
  • FailureBehaviorPolicyId? (when degrade behaviour is policy‑bound)

RSCRTriggerSetIds / RSCRTriggerKindIds: ∅ (covered by G.8:4.1) Notes (wiring‑only):

  • Rule meaning, branch taxonomy, and “probe/sandbox” semantics are governed by C.23; this module only binds ids and pins.

G.8:5.2 - G.8:Ext.AcceptanceWiring

PatternScopeId: G.8:Ext.AcceptanceWiring GPatternExtensionId: AcceptanceWiring GPatternExtensionKind: MethodSpecific GoverningPatternId: G.4 Uses: {G.4} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • AcceptanceClauseId[]
  • EvidenceProfileId[]? (if the ledger/bundle cites evidence profile ids rather than only paths)
  • PromotionPolicyId? (only if telemetry may be promoted into dominance by explicit CAL policy)

RSCRTriggerKindIds (optional delta): {RSCRTriggerKindId.PolicyPinChange} (only if acceptance policies are pinned as ids in the bundle/ledger) Notes (wiring‑only):

  • Thresholds remain governed by G.4 Acceptance; this module carries only clause ids and policy pins.

G.8:5.3 - G.8:Ext.BridgeReuseWiring

PatternScopeId: G.8:Ext.BridgeReuseWiring GPatternExtensionId: BridgeReuseWiring GPatternExtensionKind: InteropSpecific GoverningPatternId: G.7 Uses: {G.7, F.9, A.10, B.3} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum; conditional on the stated use):

  • BridgeId/BridgeCardId (the obtaining Bridge actually used; a BridgeCardId is needed only when that Card is relied on)
  • CL/CL^k/CL^plane (when cited; the applicable values are mandatory when required by the G.7 calibration or named B.3 assurance account)
  • Φ/Ψ/Φ_plane policy-ids (only the policy ids and editions required by the actual G.7 calibration or named B.3 assurance account; reference‑only and resolvable per F.8:8.1)
  • BridgeCalibrationTableId?, RegressionSetId? (both required when calibration evidence is cited, together with the row locator and active policy pins required by G.7 CC‑G7‑SCRLinkage‑1)

RSCRTriggerSetIds: {GCoreTriggerSetId.BridgeCalibrationKit} (only if the bundle/ledger explicitly binds calibration records by id) Notes (wiring‑only):

  • Present only when SoS‑LOGBundle@Context asserts cross-Context or cross-plane reuse. No additional crossing semantics are defined here.
  • The wiring MUST keep the obtaining Bridge reference, the separate bounded-use claim (use, direction, rule, and tolerated loss), and the A.10 reliance basis citable. A separate named assurance use also cites its exact target claim, receiving use, and B.3 assurance basis/result. Required CL values, policy editions, and evidence remain mandatory for that account; a supported loss penalty is applied only under the assurance policy’s declared rule, to R_eff only. Ordinary supported reuse does not require a CL shorthand, calibration record, loss-policy id, or assurance claim merely to fill the package.

G.8:5.4 - G.8:Ext.QDArchiveTelemetry

PatternScopeId: G.8:Ext.QDArchiveTelemetry GPatternExtensionId: QDArchiveTelemetry GPatternExtensionKind: MethodSpecific GoverningPatternId: C.18 Uses: {C.18, G.5} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • DescriptorMapRef.edition
  • DistanceDefRef.edition
  • EmitterPolicyRef
  • InsertionPolicyRef
  • CharacteristicSpaceRef.edition? (required iff cell boundaries / de‑dup / parity depend on the space definition)

RSCRTriggerKindIds: {RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange} Notes (wiring‑only):

  • Archive/illumination signals are telemetry; promotion into dominance is only via explicit G.4 policy pins.

G.8:5.5 - G.8:Ext.ExploreExploitTelemetry

PatternScopeId: G.8:Ext.ExploreExploitTelemetry GPatternExtensionId: ExploreExploitTelemetry GPatternExtensionKind: MethodSpecific GoverningPatternId: C.19 Uses: {C.19} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • ExploreExploitBudgetPolicyId?
  • ProbeAccountingId?

RSCRTriggerKindIds: {RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.PolicyPinChange} Notes (wiring‑only):

  • When “probe/sandbox” is used, the controlling policy ids are pinned and recorded in the ledger/bundle trace.

G.8:5.6 - G.8:Ext.OpenEndedWiring

PatternScopeId: G.8:Ext.OpenEndedWiring GPatternExtensionId: OpenEndedWiring GPatternExtensionKind: GeneratorSpecific GoverningPatternId: G.5 (generator family registry surface; algorithm semantics remain external to Part‑G core) Uses: {G.5} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • GeneratorFamilyRowRef
  • TransferRulesRef.edition
  • EnvironmentValidityRegionId?
  • CouplerPolicyId?

RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta} Notes (wiring‑only):

  • Open‑ended coverage/regret (or similar) remains telemetry unless explicitly promoted by a governing-pattern policy.