… when (i) they introduce a new kit/pack class (typically in G.2–G.5), or (ii) they are required to preserve one governing pattern per wiring extension and wiring-only separation. Method/discipline/generator specifics SHOULD default to GPatternExtension modules…
In G.Core - Discipline SoTA Kit Invariants, Defaults and Refresh Triggers (Part G)
… 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…
In G.Core - Discipline SoTA Kit Invariants, Defaults and Refresh Triggers (Part G)
G.Core establishes Part‑G‑wide invariants as delegation rules + typed catalogs + authoring discipline…
In G.Core - Discipline SoTA Kit Invariants, Defaults and Refresh Triggers (Part G)
G.Core:9 - Consequences
Positive: Part‑G patterns cite G.Core to find the governing definitions of shared invariants; refactors become safer and easier to audit.
Positive: RSCR becomes reason-code driven (typed triggers), improving traceability and preventing…
In G.Core - Discipline SoTA Kit Invariants, Defaults and Refresh Triggers (Part G)
… Core for the obligations they use (§4.2). A Builds on: G.Core entry can name that dependency. For checklist changes when a shared norm moves into G.Core, see §4.5.
Constrains:
Part‑G authoring: no shadow specs, no silent scalarization, tri‑state guards,…
In G.0 - Define Admissible Comparison and Aggregation for a Frame (CG-Spec)
Builds on: G.Core (Part-G core invariants; governing-pattern citation) GCoreLinkageManifest (normative). Effective obligations/pins/triggers are computed by union expansion of the referenced ids (per G.Core:4.2). Profiles/sets + explicit deltas; Nil‑elision…
In G.11 - Decide Whether and How to Refresh SoTA Packs and Related Results (Telemetry and Decay)
GCoreLinkageManifest (normative; canonical shape per G.Core; Nil‑elision permitted). Expand the profiles, sets and pin sets in the manifest under the G.Core expansion rule. Combine the results with the deltas stated here to obtain the effective conformance…
In G.Core - Discipline SoTA Kit Invariants, Defaults and Refresh Triggers (Part G)
G.Core:4.3.2 - Governing-definition model
TriggerGoverningDefinition := G.Core.
Any new trigger kind SHALL be added to G.Core first.
Other patterns MAY define aliases only (or cite shared alias maps), and MUST map aliases to canonical kinds…
In G.Core - Discipline SoTA Kit Invariants, Defaults and Refresh Triggers (Part G)
G.Core:3 - Forces
One governing definition vs. usability: We must centralize universal invariants, but G.x must remain readable and pattern-scoped for authors.
Delegation-first vs. completeness: Many norms already have canonical governing definitions such as…
In G.4 - CAL Authoring for a CG-Frame: Operators, Acceptance Clauses, Evidence Wiring
Builds on: G.Core (Part-G core invariants) GCoreLinkageManifest (normative). Canonical shape, Nil‑elision, and the Expansion rule are defined in G.Core. By the G.Core Expansion rule, the effective conformance ids / trigger kinds / pin obligations for G.4 are…
In G.3 - CHR Authoring for a CG‑Frame: Characteristics, Scales, Levels, Coordinates
Builds on: G.Core (Part‑G core invariants; citation/delegation hub) GCoreLinkageManifest (normative). Apply G.Core:4.2 for conformance profiles, pins, nil-elision and expansion. The manifest names the applicable trigger kinds (G.Core:4.3) and uses G.Core:4.4…
In G.10 - SoTA Pack Shipping
Builds on: G.Core (Part‑G core invariants; Default Governing Definition Index citation) GCoreLinkageManifest (G.10) (normative; expands per G.Core:4.2; Nil‑elision applies) Under Nil‑elision, compute the effective obligations, pins and triggers as…
In G.Core - Discipline SoTA Kit Invariants, Defaults and Refresh Triggers (Part G)
… suite obligations and protocol norms. Part‑G‑wide invariants are governed by G.Core so every G.x can…
In G.1 - Author a Reusable CG-Frame Generator and Selector Kit
Citation rule (normative): CC‑GCORE‑*, RSCRTriggerKindId.*, and DefaultId.* semantics are governed by their canonical definitions: primarily G.Core, and for the defaults above the definitions listed in G.Core.DefaultGoverningDefinitionIndex. G.1 MUST NOT…
In G.Core - Discipline SoTA Kit Invariants, Defaults and Refresh Triggers (Part G)
G.Core:4.6 - Explicit non-goals
G.Core does not:
introduce CG‑frame kit entities (e.g., BridgeMatrix/ReferencePlane/Φ registries); those remain in their governing G.x;
introduce method-family taxonomies, discipline packs, or generator orchestration…