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

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

GCoreLinkageManifest (normative; size‑controlled). (Canonical shape, Nil‑elision, and Expansion rule are per G.Core:4.2.)

Separation rule. Method‑/generator‑specific pins are normatively specified only inside Extensions as GPatternExtension modules (see G.8:5.*). The bundle/ledger schema may mention such fields only as extension‑gated optionals, with the authoritative pin/edition/policy requirements stated in the corresponding extension block. The core linkage manifest lists only base‑kit pins and Part‑G‑wide linkage.

`GCoreLinkageManifest := ⟨ CoreConformanceProfileIds := { GCoreConformanceProfileId.PartG.AuthoringBase, GCoreConformanceProfileId.PartG.TriStateGuard, GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted, GCoreConformanceProfileId.PartG.ShippingBoundary },

RSCRTriggerSetIds := { GCoreTriggerSetId.EvidenceGraphKit },

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

CorePinsRequired := { // Public ids governed by this pattern (strengthen conditional pins where G.8 publishes UTS publication units) UTSRowId[], // bundle/ledger/card rows + any referenced UTS rows SoS‑LOGBundleRef, SoSLogRuleId[], MethodFamilyRowRef, // exact G.5 <MethodFamilyId, rowEdition> RegistrationContext,

// Closed value sets (ids only; UTS-registered) DegradeModeEnum, MaturityRungs,

// Maturity ladder pins MaturityCardRef, // required; recommended: published as separate UTS artefact MaturityRungId?, // iff a specific rung is asserted at packaging/run-time

// Evidence / provenance pins A10EvidenceGraphRef?[], // packaging-time A.10 carriers (when PathId/PathSliceId not yet available) EvidenceGraphId?, // iff resolvable to G.6 EvidenceGraph PathId[]/PathSliceId[]?, // run-time ledgers typically have them

// Authoring traceability (SoTA-of-description) AuthoringMethodDescriptionRefs?[], // edition-pinned method-description refs },

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

(RSCR payload pins typically include: SoS‑LOGBundleRef, SoSLogRuleId[], MaturityRungId?, and EvidenceGraphId/PathId/PathSliceId?. Crossing payload pins (Bridge/CL/Φ/Ψ/Φ_plane) are introduced only when reuse is asserted, via G.8:Ext.BridgeReuseWiring. CL and loss-policy pins are required only by the actual calibration or separate named assurance use. Method-/generator‑specific payload pins are listed only inside the relevant GPatternExtension blocks in G.8:5.)

(Conditionality note for defaults.) Include DefaultId.GammaFoldForR_eff in DefaultsConsumed only if the bundle/ledger exports aggregated R_eff summaries (otherwise Nil‑elide it).