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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:40:20 UTC

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

Builds on: G.Core (Part‑G core invariants; citation/delegation hub)

GCoreLinkageManifest (normative).

GCoreLinkageManifest := ⟨ CoreConformanceProfileIds := { GCoreConformanceProfileId.PartG.AuthoringBase, GCoreConformanceProfileId.PartG.TriStateGuard, GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted }, RSCRTriggerSetIds := { GCoreTriggerSetId.BridgeCalibrationKit }, CorePinSetIds := { GCorePinSetId.PartG.CrossingVisibilityPins }, CorePinsRequired := { BridgeCalibrationTableId (BCT.id), RegressionSetId, SentinelSetId, FreshnessWindowRef, CalibrationLedgerId, RowScopeId, ReferencePlane(src)?, ReferencePlane(tgt)?, UTSRowId[]?, PathId[]?/PathSliceId[]? }, DefaultsConsumed := ∅, TriggerAliasMapRef := ∅ ⟩

  • Expansion rule. Effective CoreConformanceIds, RSCRTriggerKindIds, and CorePinsRequired are obtained by expanding the cited profile/set ids and unioning with the explicit ids above (see G.Core nil‑elision + expansion rule).
  • Conditional pins.
    • Relation, calibration and policy pins follow the channel/use conditions in G.Core:4.2.3. Source/target planes are required for an actual plane claim or another rule that consumes them; UTS and Path pins follow actual public-name and path uses.
    • BridgeCardRef.edition is required iff an F.9 BridgeCard is published as an editioned artefact.
    • Sentinel scopes MAY be recorded as PatternScopeId[] when path surfaces are not available (and SHALL then be present in sentinel records and emitted trigger payload pins).
  • CN/CG note. CC‑GCORE‑CN‑CG‑1 is included via GCoreConformanceProfileId.PartG.AuthoringBase and is exercised only when the governance card and legality gate (e.g., CNSpecRef.edition / CGSpecRef.edition) are explicitly pinned; penalty/guard policy ids (Φ(CL), Ψ(CL^k), Φ_plane) are policy pins, not governance cards or legality gates.

(payload pins, minimum: affected members of the effective CorePinsRequired (after expansion) plus any pins introduced by active extensions (e.g., QD parity pins), scoped to the watched PathSliceId[]/PathId[]/PatternScopeId[].)