FPF Reference

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

    Preface node heading:g-core-4-2-3-gcorepinsetid-catalogue-compression-primitive:114256

    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

    A GCorePinSetId is a stable identifier for a named set of commonly recurring pin obligations used in Part‑G kits. It exists solely to reduce repetition in G.x linkage sections (no new semantics).

    Conditional pins (normative). In pin‑set expansions below, a pin marked with ? is conditional: it MUST be present iff the pattern actually uses the corresponding surface/artefact class; otherwise it MAY be omitted (nil‑elision permitted) and is treated as ∅. A G.x MAY strengthen a conditional pin to unconditional by listing it explicitly in CorePinsRequired.

    GCorePinSetIdExpands to CorePinsRequired (set)Notes
    GCorePinSetId.PartG.AuthoringMinimal{CG-FrameContext, entityOfConcern := ⟨GroundingHolon, ReferencePlane⟩, CNSpecRef.edition, CGSpecRef.edition}Baseline scope+spec pins for most Part‑G authoring kits (design‑time, citable, refreshable).
    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 exact Φ, Ψ or Φ_plane policy and model actually applied; penalties remain in R/R_eff
    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-10-12 — upstream FPF commit f2bc67dd (github.com/ailev/FPF)