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:15:20 UTC

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.