Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

G.1 - Author a Reusable CG-Frame Generator and Selector Kit

Status: Stable

Tag. architectural pattern; generator chassis (design‑time kit / authoring scaffold) Normativity. normative, except sections explicitly marked informative Stage. design‑time authoring of a generator‑kit with a run‑time execution façade (policy‑governed; edition‑aware) Primary output. Publish the six cards M1…M6 as a reusable CG‑Frame kit. The versioned kit manifest, identified by CGKitId, binds all six by their card ids. Primary hooks. see §12 Relations (notably G.Core, G.0, G.2, G.5, G.10, G.11) Working‑model first (informative). prefer working models and didactic micro‑examples; escalate to formal harnesses only when risk warrants (per E.8).

Start here when. You are authoring a reusable generator, selector, or set-result scaffold rather than a one-off plan, one-off comparison, or tool-specific method recipe.

Neighboring FPF patterns. Use G.2 for the local SoTA set, G.5 for governed set-return selection, G.10 for shipping surfaces, G.11 for refresh wiring, and F.17 when the result must also land on a human-facing UTS surface.

Use another pattern when. For a one-off governed comparison, use A.19.CPM to compare an admitted profile pair under an explicit comparator, with G.0 for comparison legality; use G.5 for a shortlist. For project alignment, use A.15. When authoring a kit, make the chassis and its bindings explicit before choosing implementation tooling.

G.1:1 - Problem frame

You are authoring a CG‑Frame and want a repeatable scaffold that connects:

  • a declared scope anchor (CG‑FrameContext, entityOfConcern, governing spec refs),
  • a local SoTA set (scoped and provenance‑anchored),
  • a variant pool (candidate ideas / decision options / method variants),
  • a shortlist (a set-result outcome, not a forced singleton),
  • publication‑ready bindings into Part‑F artefacts (UTS rows, Name Cards, RSCR tests, worked examples),
  • and refresh readiness (telemetry hooks + RSCR wiring).

The chassis connects the cards. The following patterns define their methods and payloads.

  • harvesting semantics are governed by G.2,
  • selection/dispatch semantics are governed by G.5,
  • CHR/CAL payload semantics are governed by G.3 / G.4,
  • shipping semantics are governed by G.10,
  • G.11 governs refresh orchestration.

G.1:2 - Problem

Without the connections supplied by the chassis, a CG-Frame kit can have the following gaps:

  • Unscoped SoTA inputs. A reader cannot reconstruct which sources belong to the local set.
  • Generation is ad‑hoc: variant candidates are emitted without a stable trace of why/when/how.
  • Selection is opaque: eligibility/acceptance and assurance are not pinned to explicit surfaces.
  • Outputs are hard to reuse. The kit lacks the bindings needed to hand them on to UTS, RoleDescription, Concept‑Sets or RSCR.
  • No kit‑level snapshot: the scaffold lacks a versioned manifest, so downstream can’t reliably cite “which chassis edition” was used.
  • Refresh is unplanned: there is no canonical wiring from edits/telemetry/decay to RSCR causes along the P2W path.

G.1:3 - Forces

  • Breadth vs. precision: harvest wide enough to avoid local dogma, but keep the artefact actionable.
  • Generativity vs. assurance: encourage novelty while keeping evidence, legality, and trust inspectable.
  • Local meaning vs. portability: keep meaning local by default; crossing must be explicit and auditable.
  • Expressiveness vs. parsimony: resist inventing new types/slots; prefer reuse and explicit wiring.
  • Stability vs. evolution: keep stable IDs and pins while allowing SoTA, policies, and editions to evolve.
  • Didactic clarity vs. normative minimalism: authors need a concrete scaffold, but universal invariants must not be duplicated outside G.Core.

G.1:4 - Solution

G.1:4.1 - G.Core linkage (normative)

// Canonical form: see G.Core (Nil‑elision + Expansion rule for profiles/sets/pin‑sets).
GCoreLinkageManifest := ⟨
  CoreConformanceProfileIds := {
    GCoreConformanceProfileId.PartG.AuthoringBase,
    GCoreConformanceProfileId.PartG.TriStateGuard,
    GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted,
    GCoreConformanceProfileId.PartG.ShippingBoundary
  },

  CorePinSetIds := {
    GCorePinSetId.PartG.AuthoringMinimal,
    GCorePinSetId.PartG.CrossingVisibilityPins
  },

  // Prefer sets; use deltas for pattern‑specific additions.
  RSCRTriggerSetIds := { GCoreTriggerSetId.SoTAHarvestSynthesis },
  RSCRTriggerKindIds := { RSCRTriggerKindId.BaselineBindingEdit },

  // Kit identifiers governed by this pattern (the “six cards”).
  CorePinsRequired := {
    SoTAPaletteDescriptionId,
    SoTA_SetId,
    VariantPoolId,
    ShortlistId,
    CGFrameLibraryId,
    RefreshReadinessCardId,
    CGKitId,

    // Local pointer-map surface for vocabulary + observables-to-CHR anchoring.
    // (May cite `G.0:CG‑Spec.ReferenceMap`; do not duplicate semantics.)
    ReferenceMap,

    // RSCR regression tests used by the chassis (if any).
    RSCRTestId[]?,

    // For a planned baseline, identify the A.15.2 WorkPlan and local locator; add declaration ref, member designator and plan-local filling-row locator when A.15.3 applies.
    WorkPlanRef[]?
  },

  // Consumed defaults (each default cites the governing definition listed in `G.Core.DefaultGoverningDefinitionIndex`).
  DefaultsConsumed := {
    DefaultId.GammaFoldForR_eff,   // governing definition: CC-G5.4
    DefaultId.PortfolioMode,       // governing definition: CC-G5.23
    DefaultId.DominanceRegime      // governing definition: CC-G5.28
  }
⟩

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 restate or redefine those semantics.

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‑FrameContext and its binding pins:

    • entityOfConcern := ⟨GroundingHolon, ReferencePlane⟩ (pin set: PartG.AuthoringMinimal)
    • CNSpecRef.edition, CGSpecRef.edition (pin set: PartG.AuthoringMinimal)
    • ReferenceMap (cite G.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):

  • SoTAPaletteDescriptionId and SoTA_SetId bound to CG‑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):

  • VariantPoolId bound to CG‑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/or SCRId? when early assurance is recorded) and optional QD/Open‑Ended scaffolding stubs (only when introduced by explicit GPatternExtension blocks)

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.Core conformance.

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):

  • ShortlistId bound to CG‑FrameContext
  • a selected set of candidates plus rationale and SCR-addressable audit references required by G.5 (SCRId required; DRRId optional; cite PathId/PathSliceId when 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 in G.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):

  • CGFrameLibraryId bound to CG‑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)

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):

  • RefreshReadinessCardId bound to CGFrameLibraryId (and thus to CG‑FrameContext)
  • CGKitId identifies the versioned kit manifest that binds M1…M6 into 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 RSCRTriggerKindId are relevant (canonical ids), with minimal required payload pins. For a planned baseline, include the A.15.2 WorkPlan reference and its local baseline locator; filling an independently declared position under A.15.3 also 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.

G.1:4.3 - Minimal I/O surface (normative)

ModuleConsumesProduces
M1CG‑Frame brief + entityOfConcern + CNSpecRef/CGSpecRef (edition‑pinned)CG‑FrameContext + context pins
M2discovery inputs + inclusion criteria (via G.2)SoTA_SetId (+ provenance anchors; optional UTS stubs/rows)
M3SoTA_SetId + local constraints + emitter policy pins (via Extensions)VariantPoolId (+ candidate trace/provenance; optional method payload via Extensions)
M4VariantPoolId + acceptance/eligibility surfaces (via G.4/G.5)ShortlistId (selected set / set-result) + rationale refs
M5ShortlistId + CHR/CAL/LOG bundle refs + UTS/Name refsCGFrameLibraryId (library index; publish‑ready bindings)
M6telemetry inputs + applicable freshness/decay policy pins + RSCR testsCGKitId + RefreshReadinessCardId (wiring to G.11; no orchestration governance)

G.1:4.4 - Extensions (pattern‑scoped; non‑core)

All method/discipline/generator specifics MUST be expressed as GPatternExtension blocks.

Guard: G.1:Ext.* are PatternScopeId values (internal, pattern‑scoped), not new patterns and not new PatternId.

G.1:4.4.1 - GPatternExtension — G.1:Ext.HarvesterWiring

PatternScopeId: G.1:Ext.HarvesterWiring GPatternExtensionId: HarvesterWiring GPatternExtensionKind: GeneratorSpecific GoverningPatternId: G.2 Uses: {G.2} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • SoTAPaletteDescriptionId
  • SoTA_SetId
  • CoverageJudgementRef and its HarvestPolicyRef when coverage is consumed
  • ClaimSheetId[] / BridgeMatrixId (as referenced by the chosen G.2 pack form)
  • CNSpecRef.edition, CGSpecRef.edition (already required via GCorePinSetId.PartG.AuthoringMinimal)

RSCRTriggerSetIds: {GCoreTriggerSetId.SoTAHarvestSynthesis} Notes (wiring‑only). G.2 defines harvesting semantics, including living-review funnels, inclusion policy families and SoS indicator families.

G.1:4.4.2 - GPatternExtension — G.1:Ext.ShortlistWiring

PatternScopeId: G.1:Ext.ShortlistWiring GPatternExtensionId: ShortlistWiring GPatternExtensionKind: MethodSpecific GoverningPatternId: G.5 Uses: {G.5, G.4} ⊑/⊑⁺: ∅

RequiredPins/EditionPins/PolicyPins (minimum):

  • ShortlistId
  • SCRId (selector audit reference under G.5; its record carries assurance only when an actual named assurance claim is current under B.3)
  • DRRId? (only when a decision‑rationale artefact is minted)
  • TaskSignatureRef? (only for task‑templated selection)
  • AcceptanceClauseId[] (as referenced from G.4 outputs)
  • any explicit selector policy pins (policy‑id/ref; defined by the governing pattern) when not defaulted (the omitted default cites its governing definition through G.Core.DefaultGoverningDefinitionIndex)

Notes (wiring‑only). M4 binds its output to the G.5 selector/dispatcher kernel.

G.1:4.4.3 - GPatternExtension — G.1:Ext.CreativityCHR

PatternScopeId: G.1:Ext.CreativityCHR GPatternExtensionId: CreativityCHR GPatternExtensionKind: DisciplineSpecific GoverningPatternId: C.17 Uses: {C.17, G.3} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • CHRPackId? (if creativity characteristics are published/typed)
  • edition/policy pins required by the chosen creativity characteristic set (governed by C.17)

Notes (wiring‑only): G.1 only records which creativity characteristics are used for M3/M4 wiring; legality/typing lives in the CHR governing definitions.

G.1:4.4.4 - GPatternExtension — G.1:Ext.NQD

PatternScopeId: G.1:Ext.NQD GPatternExtensionId: NQD GPatternExtensionKind: MethodSpecific GoverningPatternId: C.18 Uses: {C.18, C.19} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • DescriptorMapRef.edition
  • DistanceDefRef.edition
  • InsertionPolicyRef (policy id / ref, as defined by the governing definition)
  • TaskSignatureRef? (when QD is enabled via TaskSignature flags/traits rather than by an external switch)
  • DHCMethodRef.edition? (when illumination/coverage summaries are pinned to a method)
  • EmitterPolicyRef (policy‑id/ref; identifies the chosen emitter policy under its governing definition, e.g., C.19 when E/E‑LOG is used)

RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.FreshnessOrDecayEvent}

Notes (wiring‑only): QD/QD‑adjacent algorithm families and their parameterisations belong to C.18 and C.19; G.1 only fixes the pins needed to make the VariantPool and Shortlist reproducible.

G.1:4.4.5 - GPatternExtension — G.1:Ext.OpenEndedFamilyWiring

PatternScopeId: G.1:Ext.OpenEndedFamilyWiring GPatternExtensionId: OpenEndedFamilyWiring GPatternExtensionKind: GeneratorSpecific GoverningPatternId: G.2 (family semantics are governed by SoTA cards; this block only wires pins; selector-side wiring is governed by G.5.) Uses: {G.2, G.5, C.19, C.23} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • GeneratorFamilyId[]
  • TransferRulesRef.edition (mandatory when Open‑Ended is enabled)
  • EnvironmentValidityRegionRef?
  • CoEvoCouplerRef[]?
  • SoSLogBranchId[]? (when validity of generated tasks is gated by explicit branches)

RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.FreshnessOrDecayEvent}

Notes (wiring‑only). The extension enables declared sets of {Environment, MethodFamily} pairs. It should cite/align with the selector-side wiring in G.5:Ext.OpenEndedFamilyWiring.

G.1:4.4.6 - GPatternExtension — G.1:Ext.RefreshWiring

PatternScopeId: G.1:Ext.RefreshWiring GPatternExtensionId: RefreshWiring GPatternExtensionKind: GeneratorSpecific GoverningPatternId: G.11 Uses: {G.11} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • RefreshReadinessCardId
  • RSCRTestId[]
  • canonical RSCRTriggerKindId[] emitted/recorded (aliases only as labels, if any)

RSCRTriggerSetIds: {GCoreTriggerSetId.RefreshOrchestration} Notes (wiring‑only): M6 declares readiness and wiring; orchestration semantics (queueing, prioritisation, cadence) are governed by G.11.

G.1:4.4.7 - GPatternExtension — G.1:Ext.ShippingWiring

PatternScopeId: G.1:Ext.ShippingWiring GPatternExtensionId: ShippingWiring GPatternExtensionKind: GeneratorSpecific GoverningPatternId: G.10 Uses: {G.10} ⊑/⊑⁺: ∅ RequiredPins/EditionPins/PolicyPins (minimum):

  • CGFrameLibraryId
  • SoTAPaletteDescriptionId, SoTA_SetId
  • CHRPackId?, CALPackId?, SoS‑LOGBundleId?, ParityReportId? (as present in the library index)
  • EvidenceGraphId?, BridgeMatrixId?, BridgeCalibrationTableId? (when cited by the shipped artefacts)
  • UTSRowId[]? (when any public ids are minted/published)
  • WorkPlanRef[]? with local baseline locators (when a planned baseline is cited by the shipment surface under A.15.2); include the governing declaration reference, member designator and plan-local filling-row locator when A.15.3 applies

Notes (wiring‑only). When shipping any of the kit’s artefacts, record the minimum wiring from the chassis/library index to G.10 for that shipment.

G.1:5 - Archetypal Grounding — Tell–Show–Show (informative)

Tell. Use the six cards to reconstruct the frame, sources and candidate pool used for a selected set, the artefacts indexed for publication and the changes that can trigger refresh. The manifest identifies the cards in that kit edition.

Show A (R&D multi‑criteria decisions).

  • M1: define CG‑FrameContext for “R&D decision options”, pin CNSpecRef/CGSpecRef editions, and publish entityOfConcern + ReferencePlane.
  • M2: build SoTA_SetId via G.2 using a living-review funnel with a declared update cadence and source-selection reporting (for example, PRISMA-style reporting) and publish UTS stubs for reusable constructs.
  • M3: emit a VariantPoolId where each candidate cites its emitter policy and provenance; if QD is used, wire DescriptorMapRef.edition and DistanceDefRef.edition via G.1:Ext.NQD.
  • M4: produce ShortlistId as a selected-set / shortlist surface via G.5, with acceptance predicates sourced from G.4.
  • M5: publish a CGFrameLibraryId indexing the chosen CHR/CAL/LOG bundles and UTS rows; register RSCR tests.
  • M6: declare refresh readiness (telemetry pins + canonical RSCR trigger kinds) and wire to G.11.

Show B (clinical operations; safety‑first acceptability).

  • M1: scope a CG‑Frame around dose adjustment decisions; pin legality and evidence minima explicitly.
  • M2: harvest SoTA models and safety constraints as a reconstructible set (governed by G.2).
  • M3: generate policy‑constrained candidate protocols; emitter trace and evidence pins are mandatory.
  • M4: return the shortlisted protocols as a set, which may have one member. Choosing one from a shortlist of several requires an explicit decision policy.
  • M5/M6: publish and wire refresh (decay events, policy changes, and evidence updates retrigger along the P2W path).

G.1:6 - Bias‑Annotation (informative)

  • Recency bias. To counter “newest paper wins”, apply the stated inclusion criteria under G.2 and follow any update cadence the review requires.
  • Novelty bias: over‑rewarding novelty at the expense of legality/assurance (mitigate by making acceptance and assurance pins explicit and governed).
  • Algorithmic favoritism: baking a preferred generator into “the chassis” (mitigate by keeping M3 method‑agnostic and putting method‑specific wiring into Extensions).
  • Scalarisation bias: collapsing selected sets or partial orders into a single score (mitigate by set‑return discipline pinned through G.Core).
  • Hidden‑crossing bias: unqualified reuse across contexts (mitigate by retaining the correspondence and receiving-use pins required by G.Core:4.2.3).

G.1:7 - Conformance Checklist (normative)

ConformanceIdStatement
CC‑G1‑CoreRefThe pattern MUST satisfy the effective CoreConformanceIds implied by G.1:4.1 (GCoreConformanceProfileId expansion + deltas), per G.Core expansion rules.
CC‑G1‑01The reusable CG-Frame kit MUST include all six cards M1…M6 with stable ids and a versioned kit manifest identified by CGKitId, including at minimum {CGKitId, CG‑FrameContext, SoTAPaletteDescriptionId, SoTA_SetId, VariantPoolId, ShortlistId, CGFrameLibraryId, RefreshReadinessCardId}.
CC‑G1‑02M1 MUST bind the kit to a single CG‑FrameContext and MUST expose the required pins from GCorePinSetId.PartG.AuthoringMinimal (including entityOfConcern and CNSpecRef/CGSpecRef editions). M1 MUST also expose (or explicitly cite) a ReferenceMap surface and MUST NOT restate its semantics (cite G.0:CG‑Spec.ReferenceMap).
CC‑G1‑03M2 MUST be wired to G.2 (or explicitly cite the G.2 artefacts governed by cited patterns) and MUST be reconstructible as a scoped set, including SoTAPaletteDescriptionId + SoTA_SetId (not free‑floating prose). Provenance MUST be anchored via A.10 for the emitted set.
CC‑G1‑04M3 MUST record emitter provenance as a wiring surface, including EmitterPolicyRef (policy‑id/ref), edition pins, and provenance anchors (via A.10). Any method‑specific fields MUST be introduced only via GPatternExtension blocks.
CC‑G1‑05M4 MUST be wired to G.5 (or explicitly cite G.5 artefacts governed by cited patterns) and MUST preserve set-result outcomes. SCRId MUST be present (or recoverable from an explicitly cited SCR record) so the G.5 audit references are addressable; assurance content is required only for an actual named assurance claim; DRRId SHOULD be present when a decision‑rationale artefact is minted.
CC‑G1‑06M5 MUST publish a library/index surface that points to referenced CHR/CAL/LOG artefacts and to any minted public ids (UTSRowId[], Name Cards) via the canonical governing definitions (Part F), without introducing shadow specs (delegation target: CC‑GCORE‑CN‑CG‑1 via CC‑G1‑CoreRef).
CC‑G1‑07M6 MUST publish CGKitId and expose refresh-readiness wiring: canonical RSCRTriggerKindId[] applicability, minimal payload pins and RSCR test ids. Planned baseline references MUST follow G.1:4.2.6, including the additional references required when A.15.3 applies; orchestration semantics MUST be cited to G.11.
CC‑G1‑08Any method/discipline/generator specificity in G.1 MUST be located in G.1:4.4 as GPatternExtension blocks with PatternScopeId, GPatternExtensionKind, and GoverningPatternId. If QD/illumination or Open‑Ended generator families are declared, the corresponding extension blocks MUST be present and MUST carry the edition and policy pins required by the governing pattern.

G.1:8 - Common Anti‑Patterns and How to Avoid Them (informative)

  • Anti‑pattern: “Shadow CN/CG spec inside the chassis.” Avoid: keep CN/CG as cited governing spec refs; use pins and governing definition references only.

  • Anti‑pattern: “Chassis hard‑codes a favourite algorithm.” Avoid: keep M3 core method‑agnostic; add algorithm families only via Extensions with explicit governing patterns and edition pins.

  • Anti‑pattern: “Shortlist = one winner.” Avoid: return the selected set even if it has one member. Choosing one among several selected candidates requires an explicit downstream decision rule.

  • Anti‑pattern: “Refresh plan described as prose triggers.” Avoid: record canonical RSCRTriggerKindId and payload pins; aliases only as labels and only if docked.

  • Anti-pattern: “Packaging implies shipping governance.” Avoid: treat M5 as a library index; treat M6 as readiness wiring; ship only via G.10.

G.1:9 - Consequences (informative)

  • Repeatable authoring: CG‑Frame work becomes reconstructible: what exists, what it depends on, and how it is refreshed.
  • Method pluralism with discipline: multiple generator/selector families can coexist without turning the chassis into a shadow method spec.
  • Better reuse: outputs land directly in published artefacts (UTS/Name/RSCR‑ready) rather than remaining local notes.
  • Lower refactor cost: method-wiring changes localise to Extensions; core invariants remain stable under their governing definitions.

G.1:10 - Rationale (informative)

  • Six cards keep scope, harvesting, generation, selection, publication and refresh separately inspectable and changeable.
  • Why “kit/index” rather than “pack”? A CG‑Frame authoring effort must stay modular; shipping is a separate governing boundary (G.10).
  • Why put method-specific wiring into Extensions? It prevents conflating (i) universal invariants, (ii) frame‑specific kit surfaces, and (iii) method/generator families.
  • Working models and micro-examples let authors check pins, names and boundaries before deeper formalisation.

G.1:11 - SoTA‑Echoing (informative)

The following practices connect to the chassis through its governed modules:

  • Evidence synthesis: systematic and living reviews use explicit selection criteria and source-selection reporting; living review also needs an update policy. M2 obtains these through G.2. PRISMA-style reporting can make the source selection inspectable.
  • Quality‑Diversity and archives: QD families (MAP‑Elites‑class, CMA‑ME‑class, and related archive‑based exploration) fit as M3/M4 extensions (C.18/C.19) because they require explicit descriptor/distance/insertion pins and preserve set‑valued outcomes.
  • Open‑ended exploration: open-endedness systems (POET‑class, paired/adversarial environment generation lines, and curriculum-generation approaches) fit when treated as generator‑family wiring (governed elsewhere) rather than as chassis semantics.
  • Set‑valued decision outputs: multi-objective and set‑valued evaluation practices align with the G.Core set‑return discipline, preventing hidden scalarisation.
  • Governed traceability: pinned policies and editions make the selected mechanisms and provenance inspectable across module boundaries.

G.1:12 - Relations

Builds on: G.Core, E.8, E.10, E.19. Uses: A.10 (Provenance Anchors), A.15.2 (WorkPlan baselines), A.15.3 (planned fillings of independently declared positions), A.19.CN (CN‑Spec), G.0 (CG‑Spec), G.2 (SoTA Synthesis Pack), G.3 (CHR Pack@CG‑Frame), G.4 (CAL Pack@CG‑Frame), G.5 (Selector & Dispatch), G.10 (Shipping), G.11 (Refresh Orchestration), and (via Extensions) C.17, C.18, and C.19. Publishes to / consumes from: Part‑F publication surfaces (UTS, naming, RSCR tests, Role/Concept artefacts) as cited by their governing definitions.

G.1:End

Referenced in the corpus

18 literal mentions in other sections. Read their context to establish the relation.