G.2:4 - Solution
G.2:4.1 - G.Core linkage (normative)
Builds on: G.Core (Part‑G core invariants; citation/delegation hub)
GCoreLinkageManifest (normative).
(Canonical form, Nil‑elision, and Expansion rule are defined in G.Core.)
GCoreLinkageManifest := ⟨
CoreConformanceProfileIds := {
GCoreConformanceProfileId.PartG.AuthoringBase,
GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted
},
RSCRTriggerSetIds := {GCoreTriggerSetId.SoTAHarvestSynthesis},
CorePinSetIds := {GCorePinSetId.PartG.CrossingVisibilityPins}, // expands only for actual channel/receiving-use conditions under G.Core:4.2.3
CorePinsRequired := {
// Scope pins (G.2‑specific)
CGFrameId, // identifies the exact CG-frame, which is the declared framing episteme; its cited ClaimGraph keeps source and edition, claim regions, EntityOfConcern, comparison basis, and intended use recoverable
Tradition[],
entityOfConcern := ⟨GroundingHolon, ReferencePlane⟩,
SoTA_SetId,
SoTAPaletteDescriptionId,
// Evidence / provenance pins (G.2‑specific)
CorpusLedgerId,
FlowRecordId,
EvidenceAnchorRef[],
EvidenceGraphId?,
// Crossing / synthesis pins (delta beyond CorePinSetIds; only when used)
GammaEpistSynthId[]?,
// Edition / policy pins (only when used)
HarvestPolicyRef?, // required when a coverage judgement is made
CoverageJudgementRef?, // the pack judgement, required for a relied-on coverage result
DistanceDefRef.edition?,
InclusionCriteriaId?,
ScreeningRubricId?
},
DefaultsConsumed := ∅,
TriggerAliasMapRef := ∅
⟩
(RSCR payload pins: ClaimSheetId[], SoTA_SetId, SoTAPaletteDescriptionId, BridgeMatrixId?, GammaEpistSynthId[]?, UTSRowId[]?, DistanceDefRef.edition?, HarvestPolicyRef?, InclusionCriteriaId?, ScreeningRubricId?, PathId/PathSliceId? when path‑citable evidence or a stable freshness window is pinned.)
Pattern‑local default. G.2 defines this coverage threshold outside the Part‑G-wide DefaultId set.
FamilyCoverageFloorK := 3 (unless explicitly overridden by HarvestPolicyRef and recorded in FlowRecord). This threshold supplies no counted population or same-family rule; those must be explicit before a coverage judgement. An undefined basis is unassessable, not a measured failure. Whenever coverage is judged, HarvestPolicyRef is required even when k uses this fallback; its applicability, receiving question, counted population/scope, grouping and same-family equivalence must be fixed before counting. An override changes k, not the unit or the independent pluralism duties.
Counted-family basis. The HarvestPolicy defines which candidates enter the counted population and when two entries represent the same family for this receiving question. Count equivalence classes under that rule. Repeated cards, aliases and source references for one family add zero. A combined method/generator population needs one receiving purpose and an overlap rule: a generator that is also a method is not counted twice unless the policy deliberately defines separate role-qualified units and justifies that interpretation. Freeze this basis before inspecting the count; changing it to turn a failure into three is not a repair of coverage.
The pack’s coverage judgement carries the policy/edition, counted units, deduplication basis, count, k and pass/fail result, or the exact missing basis when unassessable. Give this existing pack component a local CoverageJudgementRef for citation. Evaluate lineage and materially distinct entry plurality separately. Cards and downstream consumers cite this same judgement instead of choosing their own unit. Compare counts across packs only when their bases match, or after an explicitly justified common-basis recount.
G.2:4.2 - Kit: SoTA Synthesis Pack@CG‑Frame (surface governed by this pattern)
A conforming G.2 publication produces a notation‑independent pack whose internal organisation is free, but whose exported named components and views are stable and citable:
Each named component is addressable via a stable pack‑local identifier (e.g., CorpusLedgerId, ClaimSheetId, FlowRecordId) for citation and RSCR scoping. If any component is minted/evolved as a public id, it is published and cited via UTSRowId[] per CC‑GCORE‑UTS‑1 (delegation).
-
SoTA_Set@CG‑Frame(export view; “M2 output” consumed downstream) A read‑optimised view of the harvested candidate set for downstream generators and selectors. Constraint (normative):SoTA_Set@CG‑FrameMUST be reconstructible from pack components by id. Its coverage result cites the pack’sCoverageJudgementRef, including its fixed HarvestPolicy basis; the export view does not redefine family membership. -
G.2a CorpusLedgerLedger of candidate sources. Each row names the exact source and edition, claim region used, triage status (for example, include, park, or retire), evidence locator, and rationale for this CG-frame and receiving use. -
G.2b ClaimSheets[Tradition]Typed Claim Sheets perTradition, each with:- exact source and edition, claim region, effective ReferenceScheme where meaning matters, EntityOfConcern, and comparison basis for the stated use,
- explicit evidence anchors/citations (A.10 and/or EvidenceGraph refs when available),
- the currentness basis relevant to the claim’s use, including any applicable freshness window and risk/trust cues (cite
B.3when using trust/decay claims).
-
G.2c OperatorAndObjectInventoryInventory of candidate CHR terms (characteristics, scales and coordinates) and CAL operators or flows for downstream authoring. Cite the governing artefact and typing grounds for an entry already established as lawful. Mark the other candidates as stubs. -
G.2d BridgeMatrixA citable alignment/divergence surface acrossTradition×Tradition, with explicit losses and row scopes. If any row asserts substitution or fusion across sources or acrossTraditionrecords, the pack MUST attach aGammaEpistSynthIdrecord (alias:G.2‑F) perG.2:Ext.GammaEpistSynthesis(no silent fusion). -
G.2e MicroExamplesWorked micro-examples for load-bearing claims. Each names the exact source and edition, claim region, EntityOfConcern, comparison basis, and intended use; cites its evidence carrier or A.10 evidence-provenance path; and annotates the assurance contributions selected for that claim and use underB.3/B.3.3. When evidence-lane tags are used, cite their declared regime;C.2.2:4.6defines the KD-CALTA,VA, andLAlanes. The example card is only a publication form for those claims. -
G.2f UTSProposalsDraft Name Cards + Minimal Definitional Sheets (MDS) + alias proposals (incl. concept‑set linkage where applicable), with the required publication pins. -
G.2g entityOfConcern MapMap from key terms/claims/public ids toGroundingHolon,ReferencePlane, and minimal reference cues for later CHR/CAL authoring. -
G.2h PRISMA Flow RecordA screening/eligibility trail for how sources entered the pack (method‑profile is allowed; see Extensions). (Name is historical; the artefact remains notation‑independent.) The pack coverage judgement and its policy basis are recoverable here, separately from the lineage and material-entry pluralism results. -
G.2i SoSIndicatorFamiliesIndicator families as variants (windows/constraints/assumptions) with explicit Acceptance branches per variant (branch ids/labels only; threshold semantics belong to CAL governing definitions). -
G.2j MethodFamilyCardsCandidate method families with a shared signature and a plurality of implementations, each with validity regions, cost/complexity notes, and known failure modes. When the pack targets downstream registry/dispatch, MethodFamily cards SHOULD include the declared refs and pinsG.5needs (eligibility predicate refs, assurance profile cues, and the pack ids that justify the family). -
G.2k GeneratorFamilyCards(if applicable) Candidate generator families for environment/task generation with declared validity regions and transfer hooks. -
G.2l Annexes(optional; governing-definition-cited; see Extensions) For example: QD/NQD annexes, discipline‑specific indicator annexes, interop forms.
SoTAPaletteDescription (export view; required downstream)
Its pack-local SoTAPaletteDescriptionId identifies the view that binds these components.
- the
SoTA_Set@CG‑Frameview, ClaimSheetId[],OperatorAndObjectInventory,BridgeMatrixId?,SoSIndicatorFamilies(with variant/branch structure),MethodFamilyCards/GeneratorFamilyCards?,MicroExamples,UTSProposals,- and the
entityOfConcern Mapfor citation and later CHR/CAL authoring.
G.3/G.4/G.5 use this export view to find and cite the pack components.
Editorial template: 1‑page “SoTA Sheet” per Tradition (informative).
A one-page ClaimSheets[Tradition] template can collect the scope, claims, evidence anchors, validity region, failure modes, any applicable freshness window, cross‑Tradition reuse notes and pointers to micro‑examples.
G.2:4.3 - Harvester loop (conceptual choreography; pattern-governed)
Apply the following operations to the declared source population. A conforming pack satisfies its declared gates. When the available basis does not satisfy them, return the supported bounded result and the unmet condition; repeat a search or repair only when an attainable contribution justifies it.
-
Declare scope and plurality. Identify the exact CG-frame (the declared framing episteme), the initial
Traditionset, each intended claim region and EntityOfConcern, the comparison basis, and the receiving use. Record the cited CG-frame and source editions and evidence anchors in the pack pins rather than hiding them in a generic context field. Before counting, fix the HarvestPolicy’s receiving question, counted population, grouping and same-family equivalence, including overlap handling for a combined population. -
Discover and triage sources (ledger‑first). Populate
CorpusLedgervia:- adding seed sources,
- expansion via citation chaining and keyword family exploration,
- pruning using load‑bearing relevance tests tied to the declared CG‑Frame scope.
-
Distill claims per
Tradition. For eachTradition, author a Claim Sheet that preserves internal commitments and cites evidence anchors. Do not fuse cross‑Traditionclaims at this stage. -
Inventory operators/objects for downstream authoring. Identify candidate measurement terms and operators for downstream CHR/CAL authoring. Mark proposals as stubs. Cite an already governed CHR/CAL artefact and its grounds when reusing it. The inventory does not decide legality or set acceptance thresholds.
-
Build alignment/divergence surfaces. Where reuse across
Traditionis desired, record the obtaining correspondence and its exact basis inBridgeMatrix: F.9 for sense correspondence, C.3.3 for kind correspondence, or the direct rule for a plane relation, as actually used. State preserved distinctions and losses for the receiving question. Consolidation requires explicit alignment proof. Add bundle or gate anchors only for an independently applicable E.18 flow crossing or A.21 gate, underCC‑GCORE‑CROSS‑1. -
(Alias: G.2‑F) Construct a needed synthesis and record asserted fusion/substitution. Use B.1.3:4.4 to construct a joint conclusion from the source claims when the receiving question needs one. Recover their support and conflict relations, shared dependencies, subject and applicability before composing. A qualified synthesis with separately stated support can suffice when no common numerical model is justified.
If a
G.2pack publication asserts fusion or substitution across sources or acrossTraditionrecords (beyond mere “parallel divergent claims”), it MUST emitGammaEpistSynthIdrecords perG.2:Ext.GammaEpistSynthesis(provenance union + explicit object alignment refs + assurance tuple refs), and it MUST applyCC‑GCORE‑PEN‑1to its loss assessment and any numerical assurance penalty. -
Publish teachable micro‑groundings. Attach worked micro-examples that explain the load-bearing claim and a consequential variation in its conditions. Keep them within the claim’s supported scope. Each retains the source and edition, claim region, EntityOfConcern, comparison basis, intended use and evidence carrier or A.10 evidence-provenance path.
-
Apply gates and record repairs. Apply the fixed HarvestPolicy basis and count its distinct units before comparing coverage with
FamilyCoverageFloorK(and apply any optional diversity-by-distance gate under its own basis). Missing count semantics returns an unassessable result and the exact missing basis. If a defined gate fails:- record the failed criterion, count and basis in
FlowRecord, with the relevant corpus entries recoverable; - identify a missing relevant lineage, venue or source region that could change the result, and judge whether the available search or repair is worth undertaking for the receiving use;
- if it is, perform the search or repair and recount under the declared policy. Record what was done and the new result in
FlowRecord, citing any affectedCorpusLedgerentries. Pin the new references for any justified change to the policy or criteria and keep the earlier judgement with its original basis; - otherwise return the scoped claims and failed or incomplete pack judgement, its receiving-use limit and any precise remaining inquiry. Preserve the failed gate rather than treating the partial result as a conforming pack.
For example, an exhausted bounded population containing two method families fails a declared
k=3method-only gate. A further report about either family does not change that count. A known unexamined source region may justify another search; without one, the count and coverage failure can be the completed bounded answer. Missing population or equivalence rules instead leave the count judgement unassessable. - record the failed criterion, count and basis in
-
Emit hand‑off manifests and export views. Produce explicit manifests to:
so that downstream work can cite pack components by id rather than re‑authoring them. Each relied-on coverage result carries the same
CoverageJudgementRefand its policy basis; a downstream method-selection use cannot treat a combined method/generator count as a method-only count. The pack MUST also exportSoTA_Set@CG‑FrameandSoTAPaletteDescriptionas the default downstream consumption surfaces (ids pinned).
G.2:4.4 - Interfaces (minimal I/O Standard)
| Interface | Consumes | Produces |
|---|---|---|
| G.2-1 Harvest | exact CG-frame (the declared framing episteme) identified by CGFrameId, initial Tradition[], source edition and claim-region boundary, EntityOfConcern, comparison basis, receiving use, HarvestPolicyRef whenever coverage is judged | SoTA Synthesis Pack@CG-Frame (G.2a-G.2l) |
| G.2‑2 Extend | existing Pack + new sources/anchors + the applicable policy pins, updated if the policy changed | updated Pack + RSCR‑relevant trigger emissions (canonical kinds) |
| G.2‑3 HandOff | Pack | CHR‑handoff (to G.3), CAL‑handoff (to G.4), Registry‑handoff (to G.5) |
Note: Orchestration of re‑runs is governed by G.11; this pattern only defines what a conforming (re)harvest produces and what pins it must expose.
G.2:4.5 - Extensions (pattern‑scoped; non‑core)
Extensions are pattern‑scoped annexes. They do not introduce Part‑G‑wide norms; they declare the additional pins required when those semantics are active and cite the corresponding governing patterns.
G.2:4.5.1 - GPatternExtension: GammaEpistSynthesis
PatternScopeId: G.2:Ext.GammaEpistSynthesis
GPatternExtensionId: GammaEpistSynthesis
GPatternExtensionKind: GeneratorSpecific
GoverningPatternId: G.2
Uses: {G.Core, B.3, F.9, G.6} (penalty routing + trust/decay cues + bridges/CL + evidence path citation when used)
⊑/⊑⁺: ∅
RequiredPins/EditionPins/PolicyPins (minimum):
GammaEpistSynthId[](pack‑local ids of synthesis records; emitted iff fusion/substitution is asserted)EvidenceAnchorRef[](provenance union; evidence carriers cited by A.10 evidence-provenance paths)BridgeMatrixIdand the applicable correspondence references when a sense, kind or plane relation is used; includeBridgeCardId[]for an F.9 semantic bridgeCL/CL^planeandΦ/Ψ/Φ_plane policy-idswhen required by the cited crossing or actually used loss model (semantics and penalties →R_effremain governed by the cited definitions)PathId/PathSliceId?(only when citing viaG.6)
RSCRTriggerKindIds: {RSCRTriggerKindId.EvidenceSurfaceEdit, RSCRTriggerKindId.CrossingBundleEdit, RSCRTriggerKindId.ReferencePlaneEdit, RSCRTriggerKindId.PenaltyPolicyEdit, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.EditionPinChange}
Synthesis and its record (normative):
- For each asserted fusion/substitution, the auditable synthesis record identified by
GammaEpistSynthIdbinds: (i) provenance union, (ii) explicit object alignment refs, and (iii) assurance tuple refs underC.2.2:4.1, each tied to its exact assessed claim. A B.1.3Γ_epist^synthapplication and its returned episteme remain separate from this record. - This extension cites the
Γ‑fold,Φ, and penalty rules throughG.Coreand exposes the pins needed for replay. When B.3/C.2.2 supplies no justified common numerical score or loss calculation, retain the separate support, actual mapping limitations and bounded assurance conclusion; a synthesis record does not supply the missing model.
G.2:4.5.2 - GPatternExtension: HarvestProtocols
PatternScopeId: G.2:Ext.HarvestProtocols
GPatternExtensionId: HarvestProtocols
GPatternExtensionKind: MethodSpecific
GoverningPatternId: G.2
Uses: {B.3, A.10} (for freshness/decay and provenance anchors, when protocol requires them explicitly)
⊑/⊑⁺: ∅
RequiredPins/EditionPins/PolicyPins (minimum):
HarvestPolicyRef(declares the chosen protocol family and its parameters)FlowRecordId(protocol‑specific profile id or rubric id may be attached here)InclusionCriteriaId/ScreeningRubricId(ids only; semantics remain local to the protocol family)
RSCRTriggerKindIds: {RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.FreshnessOrDecayEvent}
Notes (extension discipline):
- This extension binds a declared protocol profile to the pack’s
FlowRecordwithout redefining evidence semantics.
G.2:4.5.3 - GPatternExtension: DHCAlignmentHooks
PatternScopeId: G.2:Ext.DHCAlignmentHooks
GPatternExtensionId: DHCAlignmentHooks
GPatternExtensionKind: DisciplineSpecific
GoverningPatternId: C.21 (DHC semantics)
Uses: {C.21, G.6, G.7} (DHC series + evidence path citations + bridge/CL regimes when alignment density is claimed)
⊑/⊑⁺: ∅
RequiredPins/EditionPins/PolicyPins (minimum):
DHCMethodRef.editionWindowRef?(if the DHC series is windowed)- exact F.17
SchemeSenseCellrefs used by the DHC comparison set (useSenseCellAddressRefwhere a durable address is needed; citeUTSRowId[]only for independently public ids) UTSRowId[]?(only if a cited cell or series id is independently minted or evolved as a public id)PathId[]/PathSliceId[](when alignment summaries cite evidence paths via G.6)
RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.EvidenceSurfaceEdit, RSCRTriggerKindId.TelemetryDelta}
Notes (extension discipline):
- If DHC alignment summaries are emitted, this extension ensures the DHC method edition and the cited evidence paths are visible.
- AlignmentDensity uses C.21’s Unit
obtaining_relations/100_compared_cells: fix the exact compared F.17 cell set and count the exact obtaining directed F.9 relations, retaining each relation’s orientation and admitted-use qualifier. Keep observed loss in its evidence account. A CL calibration label does not include or exclude a relation by itself. Any independently justified receiving-use filter must name its own policy and resulting population; it is not a C.21 CL threshold. - For example, three obtaining directed relations in a fixed set of 100 compared cells give a density of 3 in that Unit. Changing a CL label while relation truth, population and admitted-use qualifier remain fixed leaves the density 3. A fourth calibration row labelled CL=2 with no obtaining relation adds nothing. If a use condition actually changes which relations qualify, restate that changed population before comparing densities.
G.2:4.5.4 - GPatternExtension: NQDAnnex
PatternScopeId: G.2:Ext.NQDAnnex
GPatternExtensionId: NQDAnnex
GPatternExtensionKind: MethodSpecific
GoverningPatternId: C.18 (NQD-CAL semantics). C.19 governs explore/exploit logging when used.
Uses: {C.18, C.19}
⊑/⊑⁺: ∅
RequiredPins/EditionPins/PolicyPins (minimum):
DescriptorMapRef.editionDistanceDefRef.editionInsertionPolicyRef(policy‑id/ref)EmitterPolicyRef(policy‑id/ref)TaskSignatureRef?(when QD mode is trait‑gated)
RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.FreshnessOrDecayEvent}
Notes (extension discipline):
- This extension only pins the required references for replayability; it does not redefine QD semantics, dominance, or acceptance rules.
G.2:4.5.5 - GPatternExtension: InteropForms
PatternScopeId: G.2:Ext.InteropForms
GPatternExtensionId: InteropForms
GPatternExtensionKind: InteropSpecific
GoverningPatternId: G.13
Uses: {G.13}
⊑/⊑⁺: ∅
RequiredPins/EditionPins/PolicyPins (minimum):
ExternalIndexRef.editionClaimMapperRef.editionMappingPolicyRef(policy‑id/ref)UTSRowId[](for published external ids/aliases where relevant)
RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TokenizationOrNameChange, RSCRTriggerKindId.EvidenceSurfaceEdit}
Notes (extension discipline):
- Interop affects only representation and citation routes; it must not introduce alternate legality gates or acceptance semantics.
G.2:4.6 - Palette first
SoTAPaletteDescription is the base, plurality-preserving palette. Keep it recoverable while displaying a derived front, archive or shortlist. A derived view declares its own comparison, retention or choice semantics; it does not replace the base palette or silently remove its members.
When the palette’s members are traditions, TraditionPalette is the reader-facing name for that same palette declaration. For methods, hypotheses or other members, use SoTAPaletteDescription or Palette + SubjectKind.
A TraditionFront is derived under a declared Q. A TraditionArchive is derived under a declared reachability or coverage rule. Pin each view’s governing basis separately; neither view renames Tradition or changes the base palette’s meaning.
Use richer geometry or atlas language when the comparison or retention question needs it to explain the derivation. Keep that interpretation separate from the palette’s default meaning.
G.2:4.7 - Optional atlas interpretation of a declared palette
Use TraditionAtlasView only when the reader needs several derived views or interpretive qualifiers together to understand a grouping, omission risk or comparison boundary. Otherwise use the palette and its declared front, archive or shortlist, or the thinner DeclaredSubstrateInterpretiveView. A naming-only question belongs to F.18.
TraditionAtlasView specializes DeclaredSubstrateAtlasView under A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW and retains that declaration by value: the base palette, active source set or result, TypedSetViews when several declared views are combined, the space/map references and interpretive qualifiers actually used, and the connections needed to answer the inspection question. Cite SearchSpaceRef or OutcomeSpaceRef for the corresponding declared spaces. Add SpaceMetricRef, TransitionRelationRef and BridgeDistortionNote only for the comparison, reachability, transition or cross-scale claim that needs them. An OutcomeMapRef identifies a mapping from the stated result into an outcome/effect space; it does not turn the palette or result into that space. Their formal claims retain their own governing definitions.
If the interpretation changes the base source-to-outcome relation or its distortion, reopen the substrate declaration. Different atlas views may use different spaces, metrics, relations or mathematical traditions; one view does not settle those choices for every other view.