G.1:4.2 - Six‑module generator chassis (normative)
Core artefact: CGFrameReadyGeneratorKit := ⟨M1, M2, M3, M4, M5, M6⟩, where each Mi is a card with an explicit I/O surface and stable identifiers.
CGKitId identifies the versioned kit manifest (CG‑Kit@CG‑Frame) that lists the six card ids and the minimal wiring pins needed to treat the chassis as a reusable unit (this is not a shipping pack; shipping remains governed by G.10).
The chassis inventories the cards and their connections so readers can view them together. The specifications it cites define CN, CG, CHR, CAL and selection semantics.
G.1:4.2.1 - M1 — CG‑FrameContext Card (scope anchor)
Governs (kit surface):
-
CG‑FrameContextand its binding pins:entityOfConcern := ⟨GroundingHolon, ReferencePlane⟩(pin set:PartG.AuthoringMinimal)CNSpecRef.edition,CGSpecRef.edition(pin set:PartG.AuthoringMinimal)ReferenceMap(citeG.0:CG‑Spec.ReferenceMap; do not duplicate semantics)- any declared crossing/policy pins (pin set:
PartG.CrossingVisibilityPins)
Purpose: give every downstream card the same scope anchor. If the receiving criteria or comparison basis are not yet established, obtain them through G.0:4.5.1 before binding M1; reuse an adequate existing frame.
Notes: any spec-legality content is cited via A.19.CN (CN‑Spec) and G.0 (CG‑Spec) (delegation target: CC‑GCORE‑CN‑CG‑1 via CC‑G1‑CoreRef); this card does not introduce a local “mini‑spec”.
G.1:4.2.2 - M2 — SoTA_Set@CG‑Frame (harvester output card)
Governs (kit surface):
SoTAPaletteDescriptionIdandSoTA_SetIdbound toCG‑FrameContext- explicit provenance anchors for the set (via
A.10), and any published UTS stubs/rows when applicable
Governing pattern. G.2 defines the harvesting discipline and the SoTA-pack payload.
M2 binds the harvested set to the chassis. When a use relies on coverage, cite G.2’s CoverageJudgementRef with its HarvestPolicy basis, counted units and receiving question. M2 supplies no alternative family count.
G.1:4.2.3 - M3 — VariantPool (candidate inventory + emitter trace)
Governs (kit surface):
VariantPoolIdbound toCG‑FrameContext- per‑candidate minimal traceability fields (emitter identity,
EmitterPolicyRef(policy‑id/ref; defined by the governing pattern), method/generator refs when declared, edition pins, provenance anchors) - optional, per‑candidate assurance preview pointers (e.g.,
PathSliceId?and/orSCRId?when early assurance is recorded) and optional QD/Open‑Ended scaffolding stubs (only when introduced by explicitGPatternExtensionblocks)
Guardrails (via G.Core):
- tri‑state eligibility handling, penalties routing, crossing visibility, and set‑return constraints are not defined here; they are enforced via
G.Coreconformance.
Governing pattern for method payload: method‑specific emitter semantics remain in their governing definitions, cited through Extensions (e.g., the relevant C.17, C.18, and C.19 definitions).
The M3 core MUST remain a method‑agnostic inventory.
G.1:4.2.4 - M4 — Shortlist (selector output)
Governs (kit surface):
ShortlistIdbound toCG‑FrameContext- a selected set of candidates plus rationale and SCR-addressable audit references required by G.5 (
SCRIdrequired;DRRIdoptional; citePathId/PathSliceIdwhen applicable). Add assurance records only when an actual named assurance claim is current. - optional front metadata or archive metadata needed for reproducibility when used: ε‑front parameters and/or archive snapshot hooks, with governing-definition assignment through
G.5/C.18/C.19(no local semantics inG.1)
Governing pattern: selection/dispatch semantics are governed by G.5.
M4 MUST preserve set‑return semantics (as governed by G.Core) and MUST NOT hard‑code a forced singleton outcome.
G.1:4.2.5 - M5 — CG‑FrameLibrary (published bindings index)
Governs (kit surface):
-
CGFrameLibraryIdbound toCG‑FrameContext -
an index of referenced CG‑Frame artefacts ready for reuse:
- CHR/CAL/LOG bundles (by their ids; semantics governed by
G.3,G.4,G.8) - published identifiers (UTS rows, Name Cards) per Part‑F governing definitions
- additional Part‑F binding surfaces (e.g., RoleDescription templates, Concept‑Set rows) by ids locating those surfaces under their governing definitions
- RSCR test identifiers (e.g., from
F.15) and worked examples (where applicable)
- CHR/CAL/LOG bundles (by their ids; semantics governed by
Boundary: M5 is a kit/library surface, not shipping. If a shipped pack is needed, governing-definition assignment is G.10.
G.1:4.2.6 - M6 — RefreshReadiness Card (telemetry hooks + wiring)
Governs (kit surface):
RefreshReadinessCardIdbound toCGFrameLibraryId(and thus toCG‑FrameContext)CGKitIdidentifies the versioned kit manifest that bindsM1…M6into a single reusable unit. The manifest MUST enumerate the card ids and MAY cite deprecations or edition changes issued under the governing definitions.- declared telemetry hooks (what signals are observed, with what pins)
- declared RSCR wiring: which
RSCRTriggerKindIdare relevant (canonical ids), with minimal required payload pins. For a planned baseline, include theA.15.2WorkPlan reference and its local baseline locator; filling an independently declared position underA.15.3also requires the governing declaration reference, member designator and plan-local filling-row locator.
Boundary: orchestration semantics are governed by G.11.
M6 prepares refresh‑readiness metadata and wiring stubs; it does not define scheduling/priority heuristics.