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

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:50:07 UTC

G.13:4.1 - G.Core linkage (normative)

Builds on: G.Core.

GCoreLinkageManifest (normative). (Canonical form, Nil‑elision, and Expansion rule are defined in G.Core.)

`GCoreLinkageManifest := ⟨ CoreConformanceProfileIds := { GCoreConformanceProfileId.PartG.AuthoringBase, GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted, GCoreConformanceProfileId.PartG.ShippingBoundary }, RSCRTriggerSetIds := {GCoreTriggerSetId.SoTAHarvestSynthesis}, RSCRTriggerKindIds := {RSCRTriggerKindId.BaselineBindingEdit}, // delta: planned‑baseline linkage edits can be interop‑relevant

CorePinSetIds := { GCorePinSetId.PartG.AuthoringMinimal, GCorePinSetId.PartG.CrossingVisibilityPins },

CorePinsRequired := { // Interop pins (G.13‑specific; avoid duplicating GCorePinSetId.PartG.CrossingVisibilityPins) ExternalIndexRef.edition, ClaimMapperRef.edition?, MappingPolicyRef?, PlaneMapRef.edition?, ScaleEmbeddingSpecRef.edition?,

EvidenceGraphId?,
InteropSurfaceId?

},

DefaultsConsumed := {DefaultId.PortfolioMode, DefaultId.DominanceRegime} ⟩`

Payload‑pin note (informative). When emitting RSCR triggers for interop‑driven changes, payload pins should include the edited edition/policy identifiers, the impacted scope, and the applicable crossing‑visibility pins (per GCorePinSetId.PartG.CrossingVisibilityPins) when crossings/UTS/paths are involved.