G.Core:4.2 - State the applicable G.Core linkage
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.Coreand the governing definitions of the obligations used. -
When using a
GCoreLinkageManifest, identify the applicable sets or individual ids:CoreConformanceProfileIds := { GCoreConformanceProfileId… }and/orCoreConformanceIds := { CC‑GCORE‑… }RSCRTriggerSetIds := { GCoreTriggerSetId… }and/orRSCRTriggerKindIds := { RSCRTriggerKindId… }CorePinSetIds := { GCorePinSetId… }and/orCorePinsRequired := { … }(list additions or overrides when pin sets are used)DefaultsConsumed := { DefaultId… }(the governing definition is resolved throughG.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.
| GCoreConformanceProfileId | Expands 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.
| GCorePinSetId | Expands to CorePinsRequired (set) | Notes |
|---|---|---|
GCorePinSetId.PartG.AuthoringMinimal | {CG-FrameContext?, entityOfConcern := ⟨GroundingHolon, ReferencePlane⟩?, CNSpecRef.edition?, CGSpecRef.edition?} | Pin the frame, subject/plane and specification editions required by the actual kit or use. A CG-governed comparison retains its CN/CG pins; a local view, source registration or refresh judgement without that comparison uses its own required scope and source basis. |
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 use | Required references |
|---|---|
| F.9 semantic correspondence | the obtaining Bridge and its BridgeCard/source basis required by F.9; CL when the use reports or consumes that calibration |
| C.3.3 kind correspondence | exact kind endpoints and KindBridge assertion/basis; CL^k when its governing calibration or receiving rule uses it |
| Separately governed plane relation | its exact relation reference, source/target planes and direct rule; CL^plane only for a defined calibration used here |
| Numerical loss or assurance calculation | the applicable domain model and policy actually used; include Φ, Ψ or Φ_plane |