G.Core:4.2 - State the applicable G.Core linkage

Preface node heading:g-core-4-2-state-the-applicable-g-core-linkage:135738

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

Each Part-G pattern makes its applicable core obligations, pins, defaults and refresh triggers recoverable. A direct reference with its use conditions is sufficient; GCoreLinkageManifest provides a compact representation when several shared sets are used.

  • Cite G.Core and the governing definitions of the obligations used.

  • When using a GCoreLinkageManifest, identify the applicable sets or individual ids:

    • CoreConformanceProfileIds := { GCoreConformanceProfileId… } and/or CoreConformanceIds := { CC‑GCORE‑… }
    • RSCRTriggerSetIds := { GCoreTriggerSetId… } and/or RSCRTriggerKindIds := { RSCRTriggerKindId… }
    • CorePinSetIds := { GCorePinSetId… } and/or CorePinsRequired := { … } (list additions or overrides when pin sets are used)
    • DefaultsConsumed := { DefaultId… } (the governing definition is resolved through G.Core.DefaultGoverningDefinitionIndex)
    • TriggerAliasMapRef? when local trigger tokens need canonical aliases

Nil‑elision (normative size rule). Any field whose value is ∅ MAY be omitted; omission means ∅ and does not relax any obligation.

Expansion rule (normative). If profile/set ids are used, the effective CoreConformanceIds / RSCRTriggerKindIds / CorePinsRequired are the unions of their expansions plus any explicitly listed ids (see G.Core:4.2.2, G.Core:4.2.3, and G.Core:4.3.4.2).

G.Core:4.2.1 - GCoreLinkageManifest (canonical shape)

GCoreLinkageManifest groups the pattern-local references to G.Core without duplicating the governing rules.

A G.x MAY render this linkage as prose, a table, or structured notation. Its applicable ids and conditions SHALL remain recoverable:

GCoreLinkageManifest := ⟨ CoreConformanceProfileIds?: {GCoreConformanceProfileId…}, CoreConformanceIds?: {CC‑GCORE‑…}, RSCRTriggerSetIds?: {GCoreTriggerSetId…}, RSCRTriggerKindIds?: {RSCRTriggerKindId…}, CorePinSetIds?: {GCorePinSetId…}, CorePinsRequired?: {…pin ids…}, DefaultsConsumed?: {DefaultId…}, TriggerAliasMapRef?: TriggerAliasMapRef ⟩

G.Core:4.2.2 - GCoreConformanceProfileId catalogue (compression primitive)

A GCoreConformanceProfileId is a stable identifier for a named set of CC‑GCORE‑* items. Citing it in a G.x linkage section is shorthand for listing those items.

GCoreConformanceProfileIdExpands to CC‑GCORE‑* (set)Notes
GCoreConformanceProfileId.PartG.AuthoringBase{CC‑GCORE‑CN‑CG‑1, CC‑GCORE‑CROSS‑1, CC‑GCORE‑PEN‑1, CC‑GCORE‑SET‑1, CC‑GCORE‑P2W‑1, CC‑GCORE‑DEF‑1, CC‑GCORE‑TRIG‑1, CC‑GCORE‑TRIG‑2, CC‑GCORE‑TRIG‑3, CC‑GCORE‑TRIG‑4, CC‑GCORE‑ID‑1, CC‑GCORE‑ID‑2, CC‑GCORE‑LINK‑1, CC‑GCORE‑LINK‑2}Default baseline for most Part‑G kits.
GCoreConformanceProfileId.PartG.TriStateGuard{CC‑GCORE‑GUARD‑1}Add when the kit defines/consumes eligibility/guard outcomes.
GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted{CC‑GCORE‑UTS‑1}Add when the kit mints/evolves public ids (UTS rows).
GCoreConformanceProfileId.PartG.ShippingBoundary{CC‑GCORE‑SKP‑1}Add when shipping boundaries are in scope for the kit.

G.Core:4.2.3 - GCorePinSetId catalogue (compression primitive)

A GCorePinSetId is a stable identifier for a named set of pin obligations that recur in Part‑G kits. Citing it in a G.x linkage section is shorthand for listing the member obligations.

Conditional pins (normative). A pin marked with ? is required when the pattern’s actual object or receiving use calls for that surface; otherwise it may be omitted. An independently selected kit or receiving contract can require a pin explicitly. Selection of a shared pin set preserves those conditions; it does not create a CG-Frame, comparison specification, WorkPlan or crossing.

GCorePinSetIdExpands to CorePinsRequired (set)Notes
GCorePinSetId.PartG.AuthoringMinimal{CG-FrameContext?, entityOfConcern?, GroundingHolon?, ReferencePlane?, CNSpecRef.edition?, CGSpecRef.edition?}Identify what each claim concerns, including the compared targets when its rule calls for them. Name its empirical ground, plane and specification editions as required by the actual kit. A single reference may fill two roles when the entity is the same. Retain required CN/CG pins in a governed comparison. For an earlier kit carrying only ground and plane, use its source claim and frame when they identify the subject uniquely. Otherwise preserve those references and recover the missing subject before using its result.
GCorePinSetId.PartG.CrossingVisibilityPins{BridgeId?/BridgeCardId?, KindBridgeAssertionRef[]?, PlaneRelationRef[]?, BridgeMatrixId?, CL?/CL^k?/CL^plane?, Φ/Ψ/Φ_plane policy-ids?, CrossingBundleId?, UTSRowId[]?, PathId[]?/PathSliceId[]?}Activate the channel and receiving-use conditions below. Selecting this pin set alone creates no correspondence, calibration, loss model, publication row or flow/gate crossing.

CrossingVisibilityPins activation. Recover the relation and receiving use before expanding its applicable pins:

Actual claim or useRequired references
F.9 semantic correspondencethe obtaining Bridge and its BridgeCard/source basis required by F.9; CL when the use reports or consumes that calibration
C.3.3 kind correspondenceexact kind endpoints and KindBridge assertion/basis; CL^k when its governing calibration or receiving rule uses it
Separately governed plane relationits exact relation reference, source/target planes and direct rule; CL^plane only for a defined calibration used here
Numerical loss or assurance calculationthe applicable domain model and policy actually used; include Φ, Ψ or Φ_plane references when the model uses them. Any numerical assurance penalty satisfies A.6.7:4.2(2).
E.18 flow crossing, A.21 gate, public naming or path-citable reliancethe bundle, gate, UTS and path anchors required by that independently applicable rule; an edition change alone supplies none of these objects

When more than one channel is used, retain every channel's independently required basis. A no-crossing use has no crossing pins; a same-kind new entity or changed source edition alone creates no Bridge. The conditional marks permit omission only for an inactive condition, not omission of a reference required by a real calibration, assurance or gate claim.


Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)