G.Core:4.1 - Delegation-first citation for Part‑G‑wide invariants
G.Core is a citation hub, not a “second spec”. For any Part‑G‑wide invariant that already has a governing definition, G.Core:
- standardises naming via
SuiteObligations.*(A.6.7:4.2), and - records where the invariant is governed, so downstream patterns cite rather than restate.
Delegation table (normative index; no semantic duplication).
| Obligation handle | Canonical governing definition(s) | Part‑G note |
|---|---|---|
transport_declarative_only + cg_spec_cite_required_for_numeric_ops | A.6.7 + A.19.CN (CN‑Spec) + G.0 (CG‑Spec) + A.19.CHR | Cite CN‑Spec and CG‑Spec through pins rather than copying their definitions. No embedded/shadow governing specs. |
bridge_only_crossings | A.6.7 + F.9 + C.3.3 + E.18 | A claimed semantic correspondence uses F.9; a kind correspondence uses C.3.3; a plane relation keeps its own predicate. The receiving use, reliance and any authorization remain separate. G.7 calibrates these claims; no CL minimum grants the use. |
crossing_visibility_required | E.18 (CrossingBundle) + A.6.7 | Crossing visibility is a published CrossingBundle. edition_key changes on crossing‑relevant artefacts (Bridge/CL surfaces, BridgeCards, CrossingBundle registries, and UTS rows for crossing artefacts) are treated as crossing-bundle edits. If the required CrossingBundle is missing/non‑conformant, downstream consumers MUST abstain from cross-Context or cross-plane reuse (no silent crossings). |
two_bridge_rule_for_described_entity_change | A.6.7 + C.3.3 | When a use actually relies on correspondence between distinct kinds, cite the obtaining KindBridge and separately check receiving admissibility and classification. A changed entity alone establishes no kind or semantic Bridge. |
| `guard_decision_tristate(pass | degrade | abstain)+unknown_never_coerces_to_pass` |
penalties_route_to_r_eff_only | A.6.7 | Penalties affect the R lane (R_eff) only; F/G invariants must not be altered by penalties. |
no_silent_scalarisation_of_partial_orders + no_silent_totalisation | A.6.7 | Partial-order results stay set‑valued; no silent scalar ranks or “helpful” totalisation. |
planned_slot_filling_in_work_planning_only + finalize_launch_values_in_work_enactment_only + gate_decision_separation | A.15.2 + A.15.3 + A.19.CHR + A.6.7 | Edition/reference baselines use A.15.2; A.15.3 applies only to independently declared positions. Planning remains WorkPlanning‑only; launch/finalization values are WorkEnactment‑only; planning does not govern GateDecision/DecisionLog semantics. |
DefaultGoverningDefinitionIndex.single_governing_definition_per_DefaultId | this pattern | Any default names exactly one governing definition; G.Core.DefaultGoverningDefinitionIndex is an index, not a second spec. |
This pattern also governs four pieces of Part‑G‑wide infrastructure that are not already governed elsewhere:
- the typed RSCRTriggerKindId catalogue (single writer),
- the Default Governing Definition Index (one governing definition per DefaultId; index only), and
- the Δ‑discipline for ID‑stable deduplication (delegation without public‑ID breakage), and
- the linkage compression catalogues (
GCoreConformanceProfileId,GCoreTriggerSetId,GCorePinSetId) used to keepG.xlinkage sections small.