G.12:4.0 — G.Core linkage
Preface node
heading:g-12-4-0-g-core-linkage:141929
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
This pattern consumes G.Core obligations only for the branches opened.
GCoreLinkageManifest (G.12)
CoreConformanceProfileIds:={GCoreConformanceProfileId.PartG.AuthoringBase, GCoreConformanceProfileId.PartG.TriStateGuard, GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted, GCoreConformanceProfileId.PartG.ShippingBoundary}.RSCRTriggerSetIds:={GCoreTriggerSetId.BridgeCalibrationKit}only when crossing or refresh wiring is used.RSCRTriggerKindIds:={RSCRTriggerKindId.LegalitySurfaceEdit}only when a persisted series or view depends on that surface. Optional panels add only their own declared trigger kinds.DefaultsConsumed:=∅; portfolio defaults become current only throughG.12:Ext.PortfolioTelemetry.CorePinSetIds:={GCorePinSetId.PartG.AuthoringMinimal, GCorePinSetId.PartG.CrossingVisibilityPins}with nil-elision.
The minimal durable series basis is DHCSeriesRef.edition, DisciplineRef, IntendedUse, ClaimScopeRef, exact coordinate-result refs, and their windows. Each coordinate resolves the complete DHCReplayBasis from C.21. PathSliceId[], crossing pins, public-name rows, shipping pins, publication refs, and telemetry pins are conditional.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)