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 21:55:20 UTC

G.10 - SoTA Pack Shipping

Status: Stable

Use this when. Part-G output must reach a selector, auditor or maintainer as one citable, editioned shipment. Start from that receiving use, collect the required upstream references and preserve the conditions for interpreting their results. You can cite a sufficient existing result directly. Create a new pack only when the receiving use calls for a shipment.

For an independently applicable E.18 flow crossing or A.21 gate, carry its required CrossingBundle or gate anchors into the shipped pack.

Builds on: G.Core defines the shared Part‑G invariants and delegation. Cite the publications or records that define the upstream packs and kits.

Governs: shipping Part‑G outputs as a SoTA‑Pack(Core). A selector-facing outcome gets a selection/parity roster. The kit also exposes applicable PathId/PathSliceId citations and telemetry pins for refresh planning, and may include interop notes used only as citations. An inputs-only pack may omit the roster.

Cites: The definitions of CN‑Spec and CG‑Spec, CHR/CAL, selection, evidence, bridge calibration and refresh orchestration remain with their governing patterns.

G.10:1 - Problem frame — Preserve meaning when shipping

Part G produces publications and records governed by its kits and suites (harvest packs, CHR/CAL packs, evidence graphs, bridge calibration records, log bundles, parity reports). Without a defined pack boundary, shipping can become:

  • a tool-specific export without citable contents, or
  • a change to legality, defaults or selection semantics made in the course of shipping without being declared, or
  • a brittle hand‑off that cannot support RSCR/refresh (no actionable pins/editions/policies attached).

G.10 defines the single normative shipping surface for Part G, SoTA‑Pack(Core), and how to compose a pack that a selector can use and an auditor can cite. G.Core governs the shared invariants.

G.10:2 - Problem — Failures of reuse, legality and refresh

Shipping fails when:

  1. Format-as-governing-spec. A concrete export format is treated as “the pack,” turning a tool choice into a governing pack definition.
  2. Editionless hand‑offs. Shipped artefacts omit the edition/policy pins required to replay or compare outcomes, so parity and RSCR become non‑actionable.
  3. Shipping changes the rules. The pack adds local rules (hidden scalarisation, competing defaults, private gate decisions), fragmenting the governing spec ref.
  4. Invisible crossings. An actual correspondence, flow crossing or gate lacks the grounds, bundle anchors or policy pins required for its receiving use.
  5. No method‑of‑obtaining‑output disclosure. Consumers receive outcomes without a minimal, citable trail of which methods, mechanisms, and policies were used, at which editions, to obtain them.
  6. Refresh orphaning. Telemetry and decay signals exist, but the shipped artefact provides no stable scope keys (PathId / PathSliceId) and no payload pins for RSCR triggers.

G.10:3 - Forces

ForceTension
Notation independenceMake packs portable across tools ↔ still make them concrete enough to be used.
Completeness vs minimalityShip enough to be selector‑ready ↔ avoid duplicating governing definition semantics.
Continuity vs evolvabilityPreserve public IDs across edition bumps ↔ allow legitimate upgrades and deprecations.
Cross‑context reuse vs the cost of documenting crossingsEnable reuse across Traditions/contexts ↔ keep crossings explicit and auditable.
Telemetry usefulness vs semantic contaminationExport useful signals ↔ avoid turning telemetry into dominance/acceptance without pinned policy.
Fast shipping vs refreshabilityShip quickly ↔ ensure RSCR triggers can be planned and scoped (P2W‑path aware).

G.10:4 - Solution — SoTA‑Pack(Core) as the shipping object and publication kit

A SoTA‑Pack(Core) cites each upstream artefact it includes by stable ID or reference. The pack is independent of notation. It supplies the minimum pins its receiving uses need for selection, audit or refresh. These include applicable path citations and crossing bundles for audit and typed RSCR triggers for refresh.

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

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 union(expand(sets), explicit deltas).

  • CoreConformanceProfileIds := {GCoreConformanceProfileId.PartG.AuthoringBase, GCoreConformanceProfileId.PartG.TriStateGuard, GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted, GCoreConformanceProfileId.PartG.ShippingBoundary}

  • RSCRTriggerSetIds := { GCoreTriggerSetId.RefreshOrchestration } (payload pins: PackId(UTS), publicationScopeId, CNSpecRef.edition, CGSpecRef.edition, PlanItemRefs := ⟨WorkPlanRef, planLocalContentLocator⟩[], AuditPins, UTSRowId[], PathId/PathSliceId, crossing policy pins, TelemetryPinIds, relevant upstream artefact ids)

  • DefaultsConsumed := { DefaultId.PortfolioMode, DefaultId.DominanceRegime, DefaultId.GammaFoldForR_eff } Resolve their definitions through G.Core.DefaultGoverningDefinitionIndex.

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

  • CorePinsRequired (pattern delta; pin names only; id‑valued unless noted) := { PackId(UTS), publicationScopeId, contextSliceId?, PlanItemRefs := ⟨WorkPlanRef, planLocalContentLocator⟩[]? (WorkPlanning planned baseline refs), AuditPins (pack‑level pin bundle: edition pins (only on …Ref.edition), policy‑ids, UTS/Path pins; ids only), UTSRowId[], PathId[]?, PathSliceId[]?, CrossingBundleIds := CrossingBundleId[]?, TelemetryPinIds := TelemetryPinId[]?, PortfolioRosterId?, MOOManifestId? (method‑of‑obtaining‑output disclosure; conceptual object id) }

  • TriggerAliasMapRef := ∅ (canonical trigger ids are used without aliases)

Mode-specific definition pins. Use the applicable GPatternExtension blocks in G.10:4.6 for additional QD/OEE/interop pins.

G.10:4.2 - SoTA‑Pack(Core) object model (normative; notation‑independent)

SoTA‑Pack(Core) is a shipment object (a pack, not a kit and not a suite) that cites upstream artefacts and exposes pack‑level pins required for downstream use.

SoTA‑Pack(Core) :=
⟨
  PackId(UTS),
  publicationScopeId,
  contextSliceId?,
  CG-FrameContext,
  entityOfConcern := ⟨GroundingHolon, ReferencePlane⟩,

  // Governing spec refs (refs + edition pins; semantics governed by their patterns)
  CNSpecRef := ⟨A.19 ref, CNSpecRef.edition⟩,
  CGSpecRef := ⟨G.0 ref,  CGSpecRef.edition⟩,

  // Selector-facing selection/parity roster token (conceptual; no formats mandated)
  PortfolioRosterId?,        // produced by `G.10‑1` as part of composition; may cite ε and the applicable pinned regime/mode refs

  // Cited payload packs/kits (ids only; semantics governed by the cited governing patterns)
  SoTAHarvestPackId?          // e.g., G.2 output id
  CHRPackId?                  // G.3 output id
  CALPackId?                  // G.4 output id
  EvidenceGraphId?            // G.6 output id
  BridgeMatrixId?             // G.2/G.7 cited id
  BridgeCalibrationTableId?   // G.7 output id
  SoSLOGBundleId?             // G.8 output id
  ParityReportId?             // G.9 output id
  DashboardSliceId?           // G.12 output id (optional)
  InteropSurfaceId?           // G.13 output id (optional)

  // Path citation surface (ids only; semantics governed by A.10/G.6)
  PathIds := PathId[]?,
  PathSliceIds := PathSliceId[]?,

  // Planned baseline + audit pins (P2W-aware; ids only)
  PlanItemRefs := ⟨WorkPlanRef, planLocalContentLocator⟩[]?,
  AuditPins := { id pins… },                 // editions only on `…Ref.edition`; includes policies, UTS/Path pins, crossing pins

  // Crossing visibility surface (per GateCrossing; ids only)
  CrossingBundleIds := CrossingBundleId[]?,

  // Telemetry hooks for refresh planning (ids only; PathSlice-keyed; policy-id pinned)
  TelemetryPinIds := TelemetryPinId[]?,

  // Method-of-obtaining-output (MOO) disclosure (conceptual; ids only)
  MOOManifestId?,

  Notes?
⟩

PlanItemRefs, when present, resolve the exact U.WorkPlan episteme and locate the baseline content inside it. For A.15.3 content, the locator uses that WorkPlan’s planItemDesignator and any needed rowDesignator; it gives the item or row no independent identity or edition. An A.15.2 baseline stays plan content when it reuses no declaration member. A changed plan must not silently replace the earlier reference carried by the shipped pack.

G.10:4.2.1 - Portfolio roster (normative; pack-governed; governing-definition delegating)

PortfolioRosterId identifies the selector-facing roster. PortfolioRoster@Context records its citations and bindings inside the shipped publication form. It is not a kind of publication face, publication form, interop publication form or carrier.

The roster MUST NOT redefine selection or selected-set semantics (G.5) or parity semantics (G.9). Mode-specific definition pins for QD, OEE or interop come only from G.10:Ext.* blocks.

PortfolioRoster@Context :=
⟨
  PortfolioRosterId,
  PackId(UTS),
  CG-FrameContext,
  entityOfConcern,

  // Selector operation and default-resolution support
  portfolioMode?,
  dominanceRegime?,
  ε?,

  // Published selector outcome and set-result declaration (metadata fields, not local semantics)
  selectorOutcomeKind?,
  setResultFamily?,
  handoffKind?,
  subjectKind?,
  sourceSetFamily?,
  derivedViewKind?,
  sourceSetComposition?,
  basePaletteRef?,
  lensId?,
  shortlistId?,
  promotionPolicyRef?,
  retentionIntent?,

  // Selector-facing roster + provenance hooks (ids only)
  MethodFamilyRowRefs := MethodFamilyRowRef[]?,
  GeneratorFamilyRowRefs := GeneratorFamilyRowRef[]?,
  ParityReportId?,
  SCRId[]?, DRRId[]?,

  // Pin reuse: prefer referencing the enclosing pack’s AuditPins bundle
  AuditPins?,
  Notes?
⟩

The roster cites G.5 MethodFamilyRowRef = <MethodFamilyId, rowEdition> and GeneratorFamilyRowRef = <GeneratorFamilyId, rowEdition> values. A lineage id alone cannot replay the selected membership or grouping basis; each row ref resolves its immutable source edition.

Shipping these references neither admits the members nor creates their grouping. Preserve the row’s G.5 local or public registry-identity contract. A visible project-local row is not automatically a public registry entry; intentional public registration adds S1/S1′ naming and UTS duties. G.10’s independently applicable pack-shipping requirements and E.24.PUB availability conditions still apply.

Presence rule: PortfolioRosterId MAY be omitted only when the shipped pack is inputs‑only (e.g., shipping CHR/CAL/evidence without any selector‑consumable selected-set/shortlist output).

The selectorOutcomeKind, setResultFamily, handoffKind, sourceSetFamily, sourceSetComposition, derivedViewKind, basePaletteRef, lensId, and shortlistId fields carry payload metadata or references inside the shipped publication form. They do not define publication face kinds, publication form kinds, interop publication form kinds, or carrier kinds, and the rules of G.5, C.18, C.19 and G.2 remain with those patterns.

Interpretation constraints (normative by delegation). G.Core conformance requires the applicable CN or CG governing specification and its edition to be cited under its own rule. It also enforces the shared invariants for crossing visibility and penalty routing, tri-state guards, set returns, the P2W split, defaults and RSCR trigger types (CC‑G10‑CoreRef).

G.10:4.3 - Shipping procedure (normative)

Compose the pack while preserving the cited definitions:

  1. S‑1 — Gather & pin. Collect upstream artefact ids and verify the required pins implied by the linkage manifest (edition pins, policy pins, UTS/Path pins).
  2. S‑2 — Compose SoTA‑Pack(Core) + MOO disclosure. Assemble the pack object. For shipped outcomes intended for downstream use, attach a MOOManifest listing the methods, mechanisms and policies used to obtain them, with the edition of each (ids only; semantics stay with governing definitions).
  3. S‑3 — Publish the selection/parity roster. Give the selector a PortfolioRosterId with the parity and definition pins needed for reproducibility. No format is prescribed. An inputs-only pack may omit the roster under §4.2.1.
  4. S‑4 — Anchor and publish path citations. Ensure A.10 anchors exist and publish/record PathId/PathSliceId citations required for downstream explainability (e.g., the C.23 W2 AdmissibilityLedger) and maturity rung changes.
  5. S‑5 — Expose CrossingBundle. For each GateCrossing relevant to the shipped artefacts, expose the required CrossingBundle references (fail fast on missing or non‑conformant bundles when required).
  6. S‑6 — Emit telemetry pins for refresh planning. Whenever illumination increases or archive/OEE pin state changes, emit PathSlice‑keyed telemetry with policy‑id and the active …Ref.edition pins (and QD EmitterPolicyRef/InsertionPolicyRef when applicable).
  7. S‑7 — Publish to UTS (twin labels). Mint/refresh UTS Name Cards needed to cite the pack and shipped heads (Tech/Plain twins when required); a claimed cross-context semantic correspondence cites its F.9 relation, separate bounded-use claim and reliance. G.7 calibration and loss notes remain evidence for that use, not identity or permission.
  8. S‑8 — Optional: ingest interop surface. If G.13 interop is in use, ingest/cite InteropSurface@Context as annotation-only notes, pinning external index editions; do not redefine interop semantics.

G.10:4.4 - Interfaces & hooks (selector‑ and audit‑facing)

IDInterface (conceptual)ConsumesProduces
G.10‑1Compose_SoTA_PackG.* outputs, ComparatorSet, Bridges, editions, SCR/DRR deltasSoTA‑Pack(Core) (UTS row + surfaces) + AuditPins (+ MOOManifestId?) (+ PortfolioRosterId?)
G.10‑2Publish_UTSPackId(UTS), UTSRowId[], deprecation/edition‑bump notesUTS rows/Name Cards for the pack and shipped heads (incl. twins when required)
G.10‑3Expose_CrossingHooksGateCrossings, lanes/planes/contextsCrossingBundle (E.18:CrossingBundle) per GateCrossing; fail on missing/non‑conformant bundles
G.10‑4Pack_MOOreferenced method/mechanism/policy/edition idsMOOManifestId (ids only; governing-definition delegating)
G.10‑5Emit_TelemetryPinsIllumination/archive/OEE eventsPathSlice‑keyed telemetry: policy‑id, …Ref.edition (+ QD/OEE pins when applicable)
G.10‑6Publish_PathCitationsA.10 anchors, PathIdsPathId/PathSlice citations for the C.23 W2 AdmissibilityLedger & rung changes
G.10‑7Ingest_InteropSurface?(optional) G.13 InteropSurface@ContextAnnotated pack notes citing external‑index editions

Surfaces remain conceptual per E.5.2; RO‑Crate/ORKG/OpenAlex mappings belong to Annex/Interop and do not affect Core conformance.

Concrete exports and serialisations fall outside this interface set. Their definitions belong to Annex/Interop. Check conformance against G.10’s notation-independent shipping requirements and the applicable G.Core obligations.

G.10:4.5 - Consequence of governing-definition assignment (normative boundary statement)

G.10 alone defines Part G shipping, by delegation to CC‑GCORE‑SKP‑1. Other G.x patterns may produce artefacts that are shipped, but they must not embed shipping obligations; they cite G.10 shipping surfaces instead.

G.10:4.6 - Extensions (pattern‑scoped; non‑core)

All method‑/generator‑/interop‑specific shipping extension declarations live here as GPatternExtension blocks.

G.10:4.6.1 - GPatternExtension — G.10:Ext.QDArchiveShippingPins
  • PatternScopeId: G.10:Ext.QDArchiveShippingPins
  • GPatternExtensionId: QDArchiveShippingPins
  • GPatternExtensionKind: MethodSpecific
  • GoverningPatternId: C.18
  • Uses: {C.18, C.21, G.5, G.8, G.11}
  • ⊑/⊑⁺: ∅

RequiredPins/EditionPins/PolicyPins (minimum):

  • DescriptorMapRef.edition
  • DistanceDefRef.edition
  • active fields from C.21’s DHC replay basis (only when shipped archive telemetry consumes a C.21 DHC coordinate; carry exactly the fields used rather than a generic method-spec or metric-edition pin)
  • EmitterPolicyRef (policy‑id / ref)
  • InsertionPolicyRef (policy‑id / ref)
  • CharacteristicSpaceRef (id/ref; iff archive partitioning is declared)
  • characteristicSpaceDescriptionRef: U.EpistemeRef (iff partitioning depends on an exact space-definition episteme; resolve it with CharacteristicSpaceRef under A.19:5.1.1.1)
  • PathSliceId[] (to bind telemetry/refresh scope when archive behaviour is present)

RSCRTriggerSetIds: ∅ (covered by G.10 core linkage via GCoreTriggerSetId.RefreshOrchestration)

Notes (shipping-pin discipline):

  • When QD archive fields are shipped, this block specifies their required pins. C.18 defines the QD archive semantics used here.
G.10:4.6.2 - GPatternExtension — G.10:Ext.OEEShippingPins
  • PatternScopeId: G.10:Ext.OEEShippingPins
  • GPatternExtensionId: OEEShippingPins
  • GPatternExtensionKind: GeneratorSpecific
  • GoverningPatternId: G.5
  • Uses: {G.5, G.11}
  • ⊑/⊑⁺: ∅

RequiredPins/EditionPins/PolicyPins (minimum):

  • TransferRulesRef.edition
  • EnvironmentValidityRegion? (id/ref; iff a region is declared as part of generator-family support)
  • PathSliceId[] (scope key for refreshable generator telemetry when present)

RSCRTriggerSetIds: ∅ (covered by the core trigger set)

Notes (shipping-pin discipline):

  • G.5 identifies the generator-family row and its cited open-ended mode. The cited family and transfer rules define that use. The pack carries the pins needed to replay and audit the shipped claim.
G.10:4.6.3 - GPatternExtension — G.10:Ext.InteropCitation
  • PatternScopeId: G.10:Ext.InteropCitation
  • GPatternExtensionId: InteropCitation
  • GPatternExtensionKind: InteropSpecific
  • GoverningPatternId: G.13
  • Uses: {G.13}
  • ⊑/⊑⁺: ∅

RequiredPins/EditionPins/PolicyPins (minimum):

  • InteropSurfaceId
  • ExternalIndexRef.edition
  • ClaimMapperRef.edition
  • PlaneMapRef.edition?
  • MappingPolicyRef

RSCRTriggerSetIds: ∅ (covered by the core trigger set)

Notes (shipping-pin discipline):

  • Record the interop surface that contributed to the pack’s provenance. G.13 governs the crosswalk semantics.

G.10:4.7 - Metadata for shipped results and source views

Ship the metadata the receiver needs to interpret the visible result: subject and source-set kind, the declared surface pins, and any shipped selector outcome’s selectorOutcomeKind, setResultFamily or handoffKind. Use controlled tokens, cited ids or already declared head labels. The roster may carry subjectKind, sourceSetFamily, sourceSetComposition, dominanceRegime, lensId, shortlistId and applicable archive or promotion-policy ids; include those that change interpretation.

For a derived tradition view, retain derivedViewKind, basePaletteRef and its declared qId or reachability/coverage rule. portfolioMode describes selector operation; the declared result kind and source set supply the public label. These fields carry the governing palette, front, archive or selected-set meaning inside the publication. They neither redefine it nor name publication-face, publication-form, interop-form or carrier kinds.

G.10:4.7.1 - Worked publication slice
  • If the visible surface is one tradition front under the declared Q, publish sourceSetFamily=Front, derivedViewKind=TraditionFront, and identify the palette it was derived from with basePaletteRef=SoTAPaletteDescriptionId. Publish selectorOutcomeKind only when a G.5 selector outcome is also shipped, and setResultFamily only for its SetResultOutcome branch.
  • If one shortlist is emitted from that derived tradition front, publish selectorOutcomeKind=SetResultOutcome, setResultFamily=Shortlist, sourceSetFamily=Front, derivedViewKind=TraditionFront, basePaletteRef=SoTAPaletteDescriptionId, and the named lensId together.
  • If that same shortlisted surface is emitted as one stable public object, also publish shortlistId=<...> so a receiver can identify the shortlist by that token.
  • If one retained tradition archive view is shown, publish sourceSetFamily=Archive, derivedViewKind=TraditionArchive, and keep the same basePaletteRef recoverable. A G.5 selector outcome, when also shipped, carries its admitted outcome kind and, only for a SetResultOutcome, its set-result kind.
  • If the shortlist is later ordered, publish setResultFamily=RankedShortlist and keep the declared source set visible.
  • Use ChoiceSet only as a mathematical gloss when the shipped object is explicitly one mathematical analysis artifact rather than the public selected set; it is not a setResultFamily value.
  • Do not publish sourceSetFamily=TraditionPalette alone when the visible object is already one derived tradition view; readers need to know which view is on the surface and which base palette it depends on.
  • Do not publish TraditionFront or TraditionArchive as if they were the default meaning of Tradition.
  • Do not ask portfolioMode to tell the reader whether they are seeing one palette, one front, one archive, or one shortlist.

G.10:5 - Consequences

Benefits

  • A shipped result becomes selector‑ready and audit‑citable without turning file formats into governing specifications.
  • Shipping preserves the semantics of the cited outputs and their governing definitions.
  • RSCR/refresh becomes operationally viable because pack‑level scope keys and payload pins are present.

Costs / trade‑offs

  • Authors spend time recording the additional pins and publishing the pack surfaces.
  • If upstream governing definitions fail to provide citable ids/pins, apply the failure policy in the cited definitions. Shipping will stop or produce a visibly incomplete pack.

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

  • Format bias (Arch/Prag). A popular export format is tempting to treat as “the pack”. Mitigation: keep Core surfaces conceptual (E.5.2); move serialisation recipes to Annex/Interop; keep conformance on semantics.
  • Centralisation bias (Gov). A single pattern governing shipping semantics can become a bottleneck. Mitigation: keep shipping under one governing pattern, but place mode- and method-specific requirements in G.10:Ext.* extension blocks and cite governing patterns.
  • Telemetry→dominance bias (Onto/Prag). Promoting telemetry proxies (illumination/coverage) into ranking changes the interpretation of the shipped result. Mitigation: preserve the telemetry/order separation and require a CAL policy‑id for any promotion; record the policy‑id in audit pins/telemetry.
  • Interop authority bias (Onto/Epist). External indexes can silently override local legality/typing. Mitigation: G.10‑7 ingests interop only as cited notes (editions + mapping policy refs), never as a replacement governing spec ref.

G.10:7 - Archetypal grounding

World‑plane (benchmark shipping). A team working within a CG-Frame ships QD archive results (for example, from MAP-Elites-class or CMA-ME-class methods), a declared selector outcome derived from them, and generator-family results (for example, from POET-class environment generation). The shipped SoTA‑Pack(Core) cites the CHR/CAL packs and records the QD/OEE extension-required pins through the extension blocks so downstream parity and refresh can locate the affected PathSliceIds and reconsider their dependent uses.

Episteme‑plane (synthesis shipping). A team working within a CG‑Frame ships a pluralistic set of admissible methods supported by a literature review and synthesis pack. The shipped pack carries CN/CG spec refs, evidence path citations, and method‑of‑obtaining‑output disclosure; downstream selection uses set‑valued outcomes, and refresh can be scheduled when the synthesis pack or key pins change.

G.10:8 - Conformance checklist (CC‑G10)

For order and illumination, evidence, and bridge or penalty legality, apply the cited governing patterns. The following requirements govern shipping.

IDStatementVerification notes (conceptual)
CC‑G10‑CoreRefThe pattern satisfies the effective G.Core obligations declared by G.10:4.1 (after profile/set/pin‑set expansion under Nil‑elision).Check that the linkage manifest is present and that the expanded obligations are not contradicted.
CC‑G10.1 (Notation‑independent).The pack MUST NOT rely on any specific file syntax; cards/tables are conceptual; tool serialisations are informative only.Look for format‑free conceptual fields; any serialisation is explicitly non‑normative.
CC‑G10.2 (Pack parity pins).If QD archive fields are present, pin DescriptorMapRef.edition, DistanceDefRef.edition, EmitterPolicyRef and InsertionPolicyRef. Include CharacteristicSpaceRef when archive partitioning is declared, with a separate characteristicSpaceDescriptionRef: U.EpistemeRef when the exact defining episteme affects reproducibility; resolve the pair under A.19:5.1.1.1. OEE fields pin TransferRulesRef.edition under their own extension. When a shipped field consumes a C.21 DHC coordinate, carry every active field of that coordinate’s DHCReplayBasis. A non-QD generator use does not acquire QD descriptor or archive pins.Verify the corresponding G.10:Ext.* block is present and the pins appear in AuditPins and (when relevant) in telemetry pins.
CC‑G10.3 (Telemetry discipline).Any illumination increase or archive edit SHALL log PathSliceId, the active policy‑id, the active values designated by the pinned …Ref fields and the required episteme editions (including OEE TransferRulesRef.edition), and the active EmitterPolicyRef/InsertionPolicyRef when applicable.Verify emitted telemetry is PathSlice‑keyed and carries the required pins; ensure causes are recorded using canonical trigger kinds (alias labels are optional).
CC‑G10.4 (UTS publication & twins).Shipped heads use UTS Tech/Plain twins under the delegated publication rule. A shipped cross-context semantic-use claim cites its obtaining relation, separate bounded-use proposition and matching reliance; calibration summaries keep their evidence role. Kind and plane claims retain their own governors.Verify the published names and exact relation/use evidence; a visible CL or policy pin alone is insufficient.
CC‑G10.5 (MOO surfaced in shipping).For every declared selector set-result or archive published, the pack SHALL list the applicable generation/parity method and mechanism ids (e.g., QD EmitterPolicyRef/InsertionPolicyRef, parity harness ids, method refs where the method definition is generative) and the active policy‑id(s) in SCR‑visible bindings and telemetry pins (ids only; governing-definition delegating).Verify MOOManifestId is present when outcomes are intended for downstream use and does not redefine semantics.
CC‑G10.6 (Pack completeness as a citation surface).The pack cites all included upstream artefacts by id/ref and exposes the required pins (AuditPins, UTS/Path pins, CrossingBundleIds when required).Verify all present payload artefacts have ids and the pins needed to cite/replay them.
CC‑G10.7 (CrossingBundle exposure).If the shipped artefacts have relevant GateCrossings, expose the required CrossingBundleIds for each under the delegated crossing visibility rule. If there are none, record that fact. Stop shipping if a required bundle is missing or non-conformant.Check the recorded presence or absence of bundles against the shipped artefacts’ declared crossings.
CC‑G10.8 (Baseline binding is explicit when used).If the shipped pack claims a planned baseline, PlanItemRefs := ⟨WorkPlanRef, planLocalContentLocator⟩[] are present (exact WorkPlan plus plan-local content; no execution logs).Verify the baseline resolves inside the cited WorkPlan; item and row designators have no independent identity, and decision records or execution logs do not replace the plan.
CC‑G10.9 (Extension‑scoped pin declaration).If QD/OEE/interop fields are present, the corresponding GPatternExtension block is present and its required pins/editions/policies are recorded in AuditPins and in emitted telemetry pins when those pins affect refreshability.For each mode used, check that its required extension pins are present.
CC‑G10.10 (Derived tradition-view shipping).If the visible shipped surface or shortlisted source is one derived tradition view such as TraditionFront or TraditionArchive, the pack MUST publish the declared sourceSetFamily, keep basePaletteRef=SoTAPaletteDescriptionId recoverable, and carry the derivation basis (derivedViewKind, declared Q, or reachability/coverage rule id) so the reader can distinguish the visible derived view from its base palette.Verify derived tradition views are shipped as derived views, not as silent redefinitions of the base palette.

G.10:8.1 - Anti‑patterns and remedies

  • AP‑1 Format‑as‑governing‑specification. Remedy: keep Core surfaces conceptual (E.5.2); move serialisation to Annex/Interop; enforce CC‑G10.1.
  • AP‑2 Hidden edition drift. Remedy: require …Ref.edition pins in AuditPins and treat edition changes as RSCR‑relevant via canonical trigger kinds.
  • AP‑3 “QD archive present” but missing definition pins. Remedy: enforce CC‑G10.2 and the G.10:Ext.QDArchiveShippingPins pin declarations.
  • AP‑4 Telemetry silently becomes dominance. Remedy: keep telemetry report‑only unless an explicit CAL policy promotes it; require policy‑id recorded (ties to CC‑G10.3 and MOO discipline).
  • AP-5 Missing required PathSlice key. Remedy: enforce PathSlice‑keyed telemetry and path citations (G.10‑5, G.10‑6).
  • AP‑6 Cross-context reuse without its required grounds or anchors. Remedy: cite the actual relation and the receiving-use and reliance grounds required by its governor; include calibration and policy pins when that account requires them. For an independently applicable E.18 flow crossing or A.21 gate, expose its required bundle or gate anchors and fail on missing or non-conformant ones (CC‑G10.7, CC‑GCORE‑CROSS‑1).
  • AP‑7 Interop ingestion rewrites semantics. Remedy: ingest interop as cited notes only; semantics remain in G.13 (G.10‑7, G.10:Ext.InteropCitation).
  • AP‑8 Derived-view collapse. Remedy: ship sourceSetFamily, derivedViewKind, basePaletteRef, and the declared Q or reachability basis so the reader can distinguish the derived view from its base palette.

G.10:8.2 - SoTA-Echoing

  • Research‑object packaging & provenance. Research-object and RO-Crate approaches package outputs with provenance and version information. G.10 uses that packaging idea as a citation surface for independently governed outputs.
  • Reproducibility regimes in ML/AI. Reproducibility checklists, artifact evaluation and benchmark reporting motivate version pins, method disclosure, and separating telemetry summaries from decision criteria unless policy‑promoted.
  • Scholarly KG interoperability. For external mappings from systems such as ORKG or OpenAlex, G.10-7 and G.10:Ext.InteropCitation retain index editions and mapping policies as cited notes. FPF legality and typing keep their own governing definitions.

G.10:9 - Relations

Builds on: G.Core; consumes/cites artefacts governed by cited patterns from G.2 (harvest pack), G.3 (CHR pack), G.4 (CAL pack), G.6 (EvidenceGraph), G.7 (bridge calibration), G.8 (SoS‑LOG bundle), G.9 (parity report), optional G.12 (dashboard slice), optional G.13 (interop surface).

Publishes to / used by: UTS (pack identity), selector‑facing consumers (via G.5), audit and assurance publications (SCR/RSCR), refresh orchestration (G.11).

Constrains: tooling exports are downstream; serialisation and repository integration are non‑normative here.

G.10:End


Referenced in the corpus

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