G.Core:4.1 - Delegation-first citation for Part‑G‑wide invariants
For each Part G invariant already defined elsewhere, 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.
Governing definitions (normative index).
| 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 the pinned edition of each specification that governs this use (CN‑Spec, CG‑Spec or both). Keep its definition in the governing pattern. |
semantic_correspondence_requirements | A.6.7 + F.9 + C.3.3 + E.18 | A claimed semantic correspondence between different local interpretation bases 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 | When a named downstream use requires durable E.18 crossing evidence, publish the required 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 bundle required by that use is missing/non‑conformant, downstream consumers MUST abstain from that cross-Context or cross-plane use (no silent crossings). |
independent_correspondence_requirements | 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:4.2(2) | Model-bound penalty condition: apply the named model’s result meaning and applicability; loss assessment and numerical assurance penalties follow that governing clause. |
no_silent_scalarisation_of_partial_orders + no_silent_totalisation | A.6.7 | Return the set of results under the partial order. Identify any scalar ranking or extension to a total order. A scalar summary is report-only unless declared as an admissible comparator for this use (CC‑GCORE‑SET‑1). |
planned_filling_in_workplan + actual_launch_facts_and_witness + gate_decision_separation | A.15.2 + A.15.3 + A.19.CHR + A.6.7 + E.18:5.6 | A baseline adopted as planned work is A.15.2 WorkPlan content; A.15.3 applies only to typed planned filling of an independently declared argument or relation position. Preserve the planned values. An actual launch claim requires independently admitted Work and obtaining direct relations or exact application bindings; any FinalizeLaunchValues witness is a separate episteme. GateDecision/DecisionLog semantics remain with their gate governor. |
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.