G.8:4.3 - SoS‑LOGBundle@Context schema (conceptual; notation‑independent)

A conforming bundle is a UTS‑published object whose internal representation is free, but whose field meanings are stable:

SoS-LOGBundle@Context :=
⟨
  UTS.id := SoS‑LOGBundleRef,
  Edition,

  // Scope + spec pins (from GCorePinSetId.PartG.AuthoringMinimal)
  CG-FrameContext,
  entityOfConcern := ⟨GroundingHolon, ReferencePlane⟩,
  CNSpecRef.edition,
  CGSpecRef.edition,

  MethodFamilyRowRef,             // exact G.5 <MethodFamilyId, rowEdition>
  RegistrationContext,

  SoSLogRuleId[] ,               // ids only; semantics governed by C.23
  ClosedEnums: {DegradeModeEnum, MaturityRungs},  // ids only; UTS-registered closed value sets
  A10EvidenceGraphRef?[] ,        // packaging-time evidence carriers (A.10 anchors) when paths are not yet stable
  MaturityCardRef ,               // UTS ref to maturity card (required; may be embedded but MUST be citable)
  MaturityRungId? ,               // if a specific rung is asserted at packaging time

  // Optional: Acceptance wiring (thresholds remain governed by G.4)
  AcceptanceClauseId[]? ,

  // Optional: Evidence wiring (for later audit & rung transition justification)
  EvidenceGraphId? ,
  PathId[]/PathSliceId[]? ,

  // Optional: cross-context or cross-plane wiring (only when reuse is asserted)
  BridgeId/BridgeCardId? ,
  CL/CL^k/CL^plane? ,
  Φ/Ψ/Φ_plane policy-ids? ,

  // Optional: selector semantics pins (explicit value or resolved via DefaultGoverningDefinitionIndex)
  PortfolioMode? ,
  DominanceRegime? ,

  // Optional: QD / OEE pins (only when those surfaces are declared)
  CharacteristicSpaceRef.edition? ,
  DescriptorMapRef.edition? ,
  DistanceDefRef.edition? ,
  EmitterPolicyRef? ,
  InsertionPolicyRef? ,
  // Optional: Open-ended pins (only when those surfaces are declared)
  GeneratorFamilyRowRef? ,       // exact G.5 <GeneratorFamilyId, rowEdition>
  EnvironmentValidityRegionId? ,
  CouplerPolicyId? ,
  TransferRulesRef.edition? ,

  // Optional: branch/failure wiring (policy-bound)
  FailureBehaviorPolicyId? ,
  SoSLogBranchId[]? ,

  // Optional: authoring traceability (SoTA-of-description)
  AuthoringMethodDescriptionRefs?[] ,

  Notes
⟩

Bundle discipline (normative intent; semantics delegated):

• SoS‑LOGBundle@Context does not introduce new legality or normalization rules; it cites the pinned references above.
• Thresholds and numeric gates are cited by id from G.4 Acceptance (no embedding inside the bundle).
• If cross-context or cross-plane reuse is asserted, crossing pins are made explicit (Bridge/CL/Φ policy ids as required for that use by G.8:Ext.BridgeReuseWiring), and evidence paths are citable when available.

Binding obligations B1–B5 (packaging‑only; wiring‑only; semantics delegated):

• B1 — Evidence wiring. At packaging time the bundle SHOULD provide resolvable evidence refs (typically A10EvidenceGraphRef?[] and/or EvidenceGraphId?). At run time, admissibility outcomes SHOULD cite PathId/PathSliceId when available (G.6), so rung transitions and degrade/abstain traces are audit‑stable.
• B2 — CL/plane routing pins. When reuse across Context or plane is asserted, the bundle/ledger MUST cite the obtaining relation and its separate bounded-use claim and reliance basis. It MUST pin the relevant Bridge/CL/Φ/Ψ/Φ_plane policy ids required for that use by G.8:Ext.BridgeReuseWiring (reference‑only; resolvable per F.8:8.1). CL and loss-policy pins are mandatory only when required by the actual calibration or separate named assurance account. Any supported penalty MUST follow that assurance policy’s declared rule and respect the core penalty routing (penalties affect R_eff only; F/G invariance via G.Core).
• B3 — PortfolioMode/QD fields. If the bundle/ledger exposes PortfolioMode/QD fields (e.g., PortfolioMode=Archive), it MUST pin the descriptor/distance/insertion/emitter artefacts (editions/policies as applicable). Illumination remains report‑only unless explicitly promoted by a G.4 governing-pattern policy id that is pinned and recorded in the run‑time trace.
• B4 — Open‑ended fields. If the bundle binds an open‑ended generator family, it MUST pin GeneratorFamilyRowRef and TransferRulesRef.edition (and any validity region/coupler policy ids when used). Unknown transfer validity MUST be recorded as degrade/branching, not as an ad‑hoc fourth status.
• B5 — Telemetry hooks. On any material telemetry event (illumination increase, archive insertion, probe accounting update, open‑ended coverage/regret proxy update), the emitted telemetry pins SHOULD include the controlling policy ids plus the relevant edition pins (e.g., DescriptorMapRef.edition, DistanceDefRef.edition, TransferRulesRef.edition) and, when available, PathSliceId to keep RSCR planning auditable.