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.11 - Decide Whether and How to Refresh SoTA Packs and Related Results (Telemetry and Decay)

Tag. Architectural pattern (notation-independent)

Status: Stable

Normativity. Normative (unless marked informative)

Stage. run-time and maintenance-time (selective re-computation, republication, and controlled deprecation)

Primary outputs, when their use calls for them. RefreshQueue, RefreshPlan@Context (a local application name for one U.WorkPlan, not a new kind), RefreshReport@Context (record of refresh Work or its audit), DeprecationNotice@Context, and EditionBumpLog@Context. Continued reliance on an already applicable result requires none of these just to certify that refresh was omitted.

Primary hooks. G.Core (RSCR trigger catalogue, alias docking, and Default Governing Definition Index), G.6 (EvidenceGraph; PathId and PathSliceId), G.7 (Bridge Sentinels; CL, Φ, and plane policy pins), G.5 (set-returning selection and dispatch), G.8 (SoS-LOGBundle telemetry hooks), G.9 (parity reruns), G.10 (shipping hooks and pack-level telemetry pins), G.12 (dashboard telemetry pins), B.3.4 (freshness and decay), E.18 (GateCrossing and CrossingBundle visibility), C.18 and C.19 archive, front, and live-pool policy pins, C.23 (SoS-LOG branches and maturity ladders), C.28 (causal-use support results whose SoTA-sensitive fields can change downstream causal-use results).

G.11 cites G.Core for RSCR trigger-kind meaning, CN and CG admissibility, tri-state guards, penalties, set-return semantics, shipping or harvesting delegation, RSCRTriggerKindId values, and default governing definitions.

Refresh plans and reports cite the trigger meanings in G.Core and the governing definitions named in its Default Governing Definition Index.

G.11:0 - Use this when

Use this pattern when a changed premise or condition may alter whether a shipped pack or related result supports its receiving use. The change can concern evidence, source currentness, telemetry, an edition or policy, bridge calibration, a relied-on base relation definition, the named substrate edition or derivation applicability. The affected result can be an evidence set, dashboard, selected set, archive, front, Q-front, term bridge, descriptor set, parity result or use of an A.6.RCD definition.

G.11:0.1 - What goes wrong if missed

A team may rerun unrelated work, continue using an unsupported result or publish a currentness report without repairing the affected use. First determine what the changed basis permits; select and perform upkeep only where it is needed.

G.11:0.2 - What this buys

The practitioner first decides what the available support permits for the receiving use. A shared premise can reopen several dependent results while leaving independent results usable. When upkeep is justified, the refresh plan names that scope, its source and policy basis, and the selected actions. The resulting report records the work performed.

When a later or replacement source may change a claim and the receiving uses must first be found and revalidated, use A.10.1 for the bounded search frame, discovery coverage and gaps, exact-use test, the extent of the claims or actions that may need revision, application of the direct subject guidance, and the independently obtained subject result.

G.11 continues to govern source currentness, decay, refresh planning, and refresh reporting. Use a separately established currentness result or independently obtained subject result to plan later refresh under its governing pattern.

G.11:0.3 - First output

When a structured currentness line is useful for a loop, harness, workflow-store or DPF seed artifact, name its currentness object: for example, the source pack, evaluator, benchmark, harness or workflow edition, pattern seed, PFAD/PFR dependency, selected set, archive, front or publication carrier. The line can state currentness, source decay, edition change, telemetry and scoped refresh refs. Its subject pattern determines whether the artifact improved.

First establish whether the current conditions and available basis already support the receiving use. If they do, retain that result without a new currentness line, WorkPlan, waiver or skip-refresh certificate.

When a later recipient needs a changed limit or retained reason, keep the minimum useful content with the existing result or publication; a RefreshCurrentnessLine@Context can express it when a structured line is useful. Produce a RefreshPlan@Context only for selected planned refresh.

For an underlying claim about a selected set, archive, culture, bridge, evidence, dashboard or shipping, obtain that subject pattern’s result; currentness does not establish its adequacy.

When a currentness record is needed, include the applicable framework edition pins, source packs, publication-carrier currentness, deprecation, supersession and source-decay conditions.

In that record, cite E.4 for the affected framework, E.4.PFR for a framework relation, E.4.PFAD for the framework architecture decision, the exact source contribution and bounded use, including the G.2 pack when that route was used, and E.11 for discovery. For publication, cite E.17 for a source-backed face and return to source and E.24.PUB for the occurrence, form, carrier, audience, bounded use, and availability.

G.11:1 - Problem frame — Keeping shipped SoTA current without global rebuilds

Part G produces selector-ready publications and records for shipment: packs, bundles, evidence graphs, parity reports, and dashboards. Once shipped, they are exposed to:

  • telemetry (illumination and archive changes, parity outcomes, dashboard deltas),
  • currentness conditions (a relied-on premise changes, a justified review becomes due, or an actual qualification or use window ends),
  • edition drift (descriptor, distance, or transfer rules bump; policy pins evolve),
  • bridge evolution (CL or plane penalties or calibrations update).

G.11 governs the connection from typed refresh causes and their affected uses to selected plans and execution reports. G.Core supplies cause semantics and the applicable invariants.

G.11:2 - Problem — Why naive refresh breaks comparability and admissibility

A refresh loop fails when any of the following happens:

  1. Unrelated reruns. Minor edits (e.g., a single Bridge calibration) trigger pack-wide rebuilds without a traceable scope rationale.
  2. Editionless telemetry. Telemetry signals are recorded without edition pins, making reruns non-comparable and parity-unreplayable.
  3. Alias-as-semantics. Treating local trigger aliases as definitions of trigger meaning fragments refresh semantics across patterns.
  4. Silent crossings. Refresh actions implicitly change crossing assumptions (UTS, Path, or policy pins) without a visible CrossingBundle.
  5. Orchestration smuggles semantics. Refresh introduces new default behaviors (dominance, PortfolioMode, or Γ-fold) or coerces partial orders into scalars “for convenience.”

G.11:3 - Forces — Minimal recomputation under strict invariants

  • Minimal scope vs. completeness. Include every dependent use that can change, while excluding unrelated work. The resulting closure can contain several slices.
  • Operational urgency vs. auditability. Actual refresh Work must remain inspectable through the needed pins, references and paths. A currentness decision or an unchanged use must not become a fictitious Work occurrence.
  • Alias stability vs. semantic unification. Existing trigger labels must remain usable, but each must resolve by id to its governing trigger definition.
  • Modularity vs. orchestration power. G.11 must coordinate harvesting, parity, and shipping without re-implementing them or importing discipline-specific method semantics into core.
  • Policy-bound behavior vs. “smart defaults.” Ordering, priority and budget handling must follow their declared policies rather than hidden universal rules.

G.11:4 - Solution — RSCR-driven refresh as a P2W-scoped orchestration kit

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

GCoreLinkageManifest (normative; canonical shape per G.Core; Nil‑elision permitted).

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

  RSCRTriggerSetIds := {GCoreTriggerSetId.RefreshOrchestration},

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

  CorePinsRequired := {
    RSCRTriggerKindId,
    RSCRTriggerAliasId?,
    scope: PathSliceId[] | PatternScopeId,
    payloadPins{…},

    RefreshPlanId?,
    RefreshReportId?,
    DeprecationNoticeId?,
    EditionBumpLogId?,

    WorkPlanRef[]?
  },

  DefaultsConsumed := ∅,
  TriggerAliasMapRef := G.Core.TriggerAliasMap.G11
⟩

Expand the profiles, sets and pin sets in the manifest under the G.Core expansion rule. Combine the results with the deltas stated here to obtain the effective conformance ids, trigger kinds and required pins.

TriggerAliasIds (visible; labels only). {G.11:T0…T7} (resolved through TriggerAliasMapRef; G.Core defines the trigger meanings).

G.11:4.2 - Refresh orchestration kit (subject-qualified; conceptual artefacts)

Use the following artifacts for refresh planning and reporting. RefreshPlanId is required on a plan and RefreshReportId on a report. The linkage manifest applies to the triggers and actions that occur; retaining applicable support creates no trigger, plan or report merely to fill their pins.

  1. RefreshQueue (conceptual queue). A queue of refresh candidates keyed by affected scope (PathSliceId refs preferred where graph-expressed; PatternScopeId permitted). One candidate may cover several dependent slices. Ordering, prioritization and batching use declared policies; every queue item carries canonical trigger kind ids.

  2. RefreshPlan@Context (one U.WorkPlan). The plan for a refresh is a U.WorkPlan episteme under A.15.2. It declares intended Work and establishes no performed occurrence. Keep gate decisions outside the plan. RefreshPlan@Context is this pattern’s name for that plan. The plan declares:

    • RefreshPlanId (UTS-published id; editioned)
    • EntityOfConcernRef and ReferencePlane pins (by ref; no implicit widening)
    • TargetScope := PathSliceId[] | PatternScopeId[]
    • PlannedTriggers := RSCRTrigger[] (canonical trigger kind ids, scope, and payload pins)
    • PlannedActions := RefreshAction[] (each action delegates to a subject pattern)
    • RequiredPins: exact affected source and result editions, policy pins and scope for replayability; UTS pins for public identities used; graph Path pins when the selected scope is graph-expressed or an independently applicable receiving contract requires them.
    • PlannedFillingRows[]? as ClaimGraph content kept inside the WorkPlan under A.15.3 when a value must be pinned against a declaration member defined by its own pattern. A row is addressed only through the WorkPlan and has no separate reference or identity.
  3. RefreshReport@Context (record of refresh Work or its audit). An execution or audit report that records:

    • RefreshReportId (UTS-published id; editioned)
    • ExecutedActions[] with independently admitted A.15.1 Work refs and references to their performers identified under A.13, plus links to the resulting artifacts under their subject patterns (for example, a new parity report or pack id). Add F.6 attribution only when the receiving use needs to attribute the Work to its established A.13 assignment.
    • ObservedDeltas (telemetry deltas, admissibility changes, evidence-relation or source-relation changes) as refs and pins, not as untyped prose
    • RSCRRefs[] (any RSCR or regression harness artefacts invoked)
    • EmittedNotices[] := DeprecationNoticeId[] and EditionBumpLogId[]
    • the canonical trigger kinds applied, even when an alias was used
  4. DeprecationNotice@Context and EditionBumpLog@Context. Controlled evolution artefacts that preserve ID-continuity:

    • DeprecationNotice explains scope, reason class (canonical trigger kind ids), and successor refs.
    • EditionBumpLog records edition increments and the pins that justify them.

    G.Core governs ID continuity and the use of aliases.

G.11:4.2a - Selected-set, archive, and cultural-variant currentness

Use this line when a recipient needs a structured currentness result concerning a selected set, front, Q-front, archive, portfolio lineage, cultural-variant lineage, style or tradition term bridge, path slice, reused A.6.RCD predicate definition, or admitted derived relation kind.

RefreshCurrentnessLine@Context:
  governedObjectRef:
  currentnessObjectKind:
  sourceRecordRef:
  editionOrLineagePins:
  affectedPathSliceOrScope:
  subjectPatternLocator:
  receivingUseAndApplicableConditions:
  currentnessConclusion:
  plannedRefreshAction?:
  refreshReportRef?:

currentnessObjectKind may name, for example, a selected set, Front, Q-front, ExplorationArchive, Archive, a cultural lineage, a term bridge, or a reused predicate definition.

Use the line only when its recipient needs this structured currentness result; identify the temporal reference and relevant window within its conditions and pins. plannedRefreshAction? is absent when no refresh is selected, and refreshReportRef? is absent when no such report exists.

The line states applicability for a use, not that the subject claim is true or adequately supported. Use G.5 for selected-set declaration, E.17 and E.24.PUB for publication, C.18 for archive and front relations, C.19 for pool treatment, C.36 for cultural-evolution claims, F.17 for exact local SchemeSenseCells, F.18 for name settlement, F.9 for obtaining Bridges, and A.6.RCD for a derived relation kind.

Use the existing result or publication for a needed currentness conclusion or limitation. Use RefreshPlan@Context, RefreshReport@Context, DeprecationNotice@Context or EditionBumpLog@Context when the corresponding plan, performed work, deprecation or edition change occurs; do not add an empty ticket or notice for unchanged applicability.

When the governed object is a reusable A.6.RCD predicate definition or an admitted derived relation kind, the currentness line pins the exact base definitions, named substrate and edition, authorized derivation operation, and applicability scope. A change to any of them reopens the affected derivation and its dependent uses under A.6.RCD; G.11 schedules the bounded refresh but does not redefine the relation or derivation.

G.11:4.3 - Orchestration semantics (conceptual; delegating to governing definitions)

Use G.11 to plan scoped actions from typed causes; action semantics remain with their subject patterns.

4.3.1 Ingestion. Consume RSCR triggers from:

  • telemetry hooks (e.g., G.8, G.10, G.12),
  • freshness and decay events (B.3.4),
  • evidence, bridge, policy, edition, relied-on base-definition, named-substrate-edition, or derivation-applicability edits (from the respective subject patterns’ publication faces, forms, or units).

Normalize each ingested signal into an RSCRTrigger with its canonical id, scope and payload pins; retain an alias label when used.

4.3.2 Scope closure over the actual dependencies. Start from the changed premise and the receiving question. Establish the minimal dependency closure that includes every dependent use whose claim, action or required check can change. Minimality excludes unrelated uses. A smaller node count or the first slice found can leave a dependent use out. Follow:

  • cited evidence and source relations, using G.6 PathId and PathSliceId refs where those dependencies are graph-expressed;
  • declared crossings, including G.7 sentinels and required CrossingBundle visibility; and
  • pinned editions and policies consumed by the receiving result.

Recover the exact direct use at each step. A common evidence item, causal assumption, calibration or policy can feed several paths and a result that combines them. Include those branches and the combining use before choosing actions.

Repeated citations to one basis do not make it independent support. G.6 provides the representation and indexes; A.10.1 supplies source-change discovery, direct-use tests and coverage limits when the existing account is insufficient.

Graph reachability alone establishes no dependence. Keep an unresolved branch explicit and continue independently resolved branches.

For a nongraph result, name the exact source, receiving result/use and dependency under PatternScopeId. Use PathSliceId when the scope is graph-expressed or independently required by the receiving contract.

This closure states which conclusions need reconsideration; it neither performs their subject judgement nor commits every affected use to a rerun.

Apply the subject rules with available evidence. An affected branch may retain the same supported conclusion, acquire a narrower use, need refresh or require suspension; an independent result remains reusable on its own qualified basis.

Interpret a B.3.4 trigger for the receiving claim and use. Age alone does not select a disposition. Stop when the present basis gives the warranted answer; keep only a limitation or reason that a later recipient needs. If a subject judgement reveals another consequential dependency, return it to the scope before planning dependent work.

4.3.3 Planning (P2W boundary). Use C.11.DUA to compare further inquiry with the warranted answer already available. Select an attainable action for what it can change at the receiving horizon, including its full cost, delay and displaced work. C.11 and, where applicable, C.19.2 supply the choice; binding evidence and authority requirements remain in force. Produce RefreshPlan@Context only for the planned actions selected. Possible action forms include:

  • RerunHarvest (delegates to the selected harvesting or SoTA method, such as G.2; use G.1 additionally only when its generator-kit cards or wiring must change)
  • RerunParity (delegates to G.9)
  • RecomputeSelectionOrSetResult (delegates to G.5)
  • RebindBridgeOrCrossing (delegates changes to the obtaining Bridge to F.9, calibration-record changes to G.7, and crossing visibility to E.18 and the applicable visibility harnesses)
  • UpdateEvidenceBindings (updates the provenance representation under G.6 after any changed direct relation or subject result has been established under its own governor)
  • ReshipPack (delegates to G.10)
  • UpdateBundle (delegates to G.8)
  • UpdateDashboardSlice (delegates to G.12)
  • EmitDeprecationNotice or EmitEditionBumpLog (publication units governed by this pattern)

4.3.4 Execution and audit. When selected actions are performed as Work or Work-bound audit, identify the actual performers and independently admitted occurrences and publish the corresponding RefreshReport@Context.

Assess the returned subject results for each receiving use, including any result that combines refreshed and retained branches. Reuse sufficient existing observations where applicable; a plan supplies no new observation or performance.

When a gate applies, record its G.Core outcome (pass, degrade or abstain) with the policy IDs and cited evidence or source relations.

G.11:4.3a - Causal-use refresh sentinels

When a shipped result consumes C.28, inspect the following changes when they can alter supported or unsupported use, a support-result verdict, its limits or a downstream decision basis:

SentinelAffected resultRefresh pins
sampling-realizability shiftCounterfactualSamplingRealizabilityResulttarget distribution, decision Method and any derivation, physical, ethical, operational, and history constraints, required sampling construction or obstruction, unresolved questions, status, supported use, and unsupported use
performed sampling or resulting-data shiftdated sampling Work plus A.10 evidence path and empirical data regimeWorkPlan when used; actual performer identified through A.13; dated Work independently admitted through A.15.1; Method and window; resulting sample or data; provenance and currentness. Add F.6 with the same A.13 assignment only if the refresh decision needs to attribute the Work to that assignment. F.6 identifies neither performer nor assignment. A missing or failed attribution alone leaves independently admitted Work intact. If the finding invalidates a consumed A.13 or A.15.1 premise, recheck that premise and its dependent conclusions. A realizability result cannot substitute for the sampling Work or the resulting data.
identification or bound shiftCausalIdentificationResultdata-regime refs, assumptions, identifying derivation, bound or failure witness, sensitivity
estimate shiftCausalEstimateResultidentification or design basis, data, estimator Method, diagnostics, uncertainty, sensitivity, and any live estimation-consistency result
target-trial practice shiftprotocol and mapping resultsquestion/estimand, protocol-to-data mapping, assumptions, estimate/precision, sensitivity and reporting source edition
causal-fairness shiftC.28 support result plus D.5 BiasAuditReport@Contextfairness estimand, extra counterfactual-identification assumptions, estimate and consistency result when used, support components and result, affected population, audit limits, and decision
causal-representation shiftCausalVariableRepresentationRecordintervention validity, invariance, abstraction fidelity, query preservation, shift and use limits
off-policy or causal-RL shiftOffPolicyCausalEvaluationResultbehaviour/evaluation policies, horizon/history, confounding, overlap, endpoints, estimator and uncertainty
simulation-validation shiftsimulationResultRef in CausalSupportComponentRefsmodel assumptions, validation, sensitivity, supported model use and unsupported realized/interventional use
transport-endpoint shiftCausalTransportabilityResultsource/target population, domain, environment and data-generating regime, assumptions, windows, formula and unresolved limits

These are payload distinctions under existing G.Core trigger kinds. Apply §4.3.2 to every result and receiving use that consumes the changed causal basis, including several results sharing an assumption or data source.

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

Discipline-specific refresh strategies and generator-specific wiring use GPatternExtension blocks. Queue scheduling uses the policy pins on RefreshQueue and RefreshPlan@Context described in §4.4a. A.15.2 and A.15.3 keep the WorkPlan and its local content separate from dated Work.

G.11:4.4.1 - GPatternExtension — G.11:Ext.TriggerAliases
  • PatternScopeId: G.11:Ext.TriggerAliases
  • GPatternExtensionId: TriggerAliases
  • GPatternExtensionKind: InteropSpecific (alias docking)
  • GoverningPatternId: G.Core
  • Uses: {G.Core} (cites G.Core.TriggerAliasMap.G11)
  • ⊑ and ⊑⁺: ∅

Required pins, edition pins, and policy pins (minimum):

  • RSCRTriggerKindId[] (canonical ids recorded on triggers)
  • RSCRTriggerAliasId? (e.g., G.11:T0…T7 as labels only)
  • scope: PathSliceId[] | PatternScopeId

RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.FreshnessOrDecayEvent, RSCRTriggerKindId.CrossingBundleEdit, RSCRTriggerKindId.PenaltyPolicyEdit, RSCRTriggerKindId.MaturityRungChange, RSCRTriggerKindId.EvidenceSurfaceEdit}

Notes (wiring-only): Keep the labels T0…T7 and resolve them through G.Core.TriggerAliasMap.G11.

G.11:4.4.2 - GPatternExtension — G.11:Ext.DecayAndDebt
  • PatternScopeId: G.11:Ext.DecayAndDebt
  • GPatternExtensionId: DecayAndDebt
  • GPatternExtensionKind: DisciplineSpecific
  • GoverningPatternId: B.3.4 (use-qualified currentness and interpreted planning debt)
  • Uses: {B.3.4, G.6}
  • ⊑ and ⊑⁺: ∅

Required pins, edition pins, and policy pins (minimum):

  • The receiving claim/use and the changed premise or applicable review condition, with source references where published.
  • FreshnessWindowDeclRef?, DecayPolicyIdRef? or EpistemicDebtBudgetRef? only when the adopted window, deterioration model or planning measure is used. Their source supplies the meaning; no default expiry or debt budget is required.
  • The affected dependent claims and uses, expressed as PatternScopeId for nongraph scope or PathSliceId[] for graph scope. Retain graph pins when an independently applicable profile requires them; carrier age alone does not select every use of that carrier.

RSCRTriggerKindIds: {RSCRTriggerKindId.FreshnessOrDecayEvent, RSCRTriggerKindId.EvidenceSurfaceEdit, RSCRTriggerKindId.BaselineBindingEdit}

Notes (wiring-only): B.3.4 determines what the trigger means for the use. Depending on the grounds, continue, narrow or suspend the use, refresh the affected result, or apply an authorized exception. The trigger neither imposes a Refresh/Deprecate/Waive triad nor automatically downgrades the result. Currentness is not assurance of the underlying claim. Budget and priority logic apply only when their interpreted policies are used.

G.11:4.4.3 - GPatternExtension — G.11:Ext.QDRefreshWiring
  • PatternScopeId: G.11:Ext.QDRefreshWiring
  • GPatternExtensionId: QDRefreshWiring
  • GPatternExtensionKind: MethodSpecific
  • GoverningPatternId: C.18 (QD semantics; descriptor, distance, and insertion)
  • Uses: {C.18, C.19, G.5, G.8}
  • ⊑ and ⊑⁺: ∅

Required pins, edition pins, and policy pins (minimum):

  • DescriptorMapRef.edition, DistanceDefRef.edition
  • CharacteristicSpaceRef with separate characteristicSpaceDescriptionRef: U.EpistemeRef (required when a domain-family coordinate is declared by the QD governing definition; resolve the same-space pair under A.19:5.1.1.1)
  • InsertionPolicyRef, EmitterPolicyRef (policy-bound)
  • Archive or illumination scope and policy-id for each emitted telemetry trigger: PatternScopeId for nongraph scope; PathSliceId when graph-expressed or required by an independently applicable parity, evidence or shipping contract.

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

Notes (wiring-only): Pin the QD inputs so the reruns can be compared. C.18 governs their QD meaning.

G.11:4.4.4 - GPatternExtension — G.11:Ext.OEERefreshWiring
  • PatternScopeId: G.11:Ext.OEERefreshWiring
  • GPatternExtensionId: OEERefreshWiring
  • GPatternExtensionKind: MethodSpecific
  • GoverningPatternId: C.19 (open-ended exploration and exploration-exploitation logistics)
  • Uses: {C.19, G.5, G.8, G.9}
  • ⊑ and ⊑⁺: ∅

Required pins, edition pins, and policy pins (minimum):

  • TransferRulesRef.edition, EnvironmentValidityRegion (when OEE is declared by the subject patterns)
  • GeneratorFamilyRowRef = <GeneratorFamilyId, rowEdition> and TransferRulesRef wiring pins (as published by G.5 and the governing definitions); resolve the row edition used by the affected result
  • telemetry scope and policy-id for each emitted trigger: PatternScopeId for nongraph scope; PathSliceId when graph-expressed or required by an independently applicable parity, evidence or shipping contract.

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

Notes (wiring-only): This module connects OEE refresh triggers to comparable reruns. The governing definition supplies OEE method semantics.

G.11:4.4a - Scheduling and priority policy pins

Scheduling strategies (bandit-style allocation, queueing, cadence policies, early stopping, or manual priority rules) may influence the order and budget of refresh work, but they do not define trigger meaning, action semantics, parity semantics, shipping semantics, or Part-G-wide defaults.

G.11 therefore treats scheduling as policy-bound refresh planning:

  • RefreshPriorityPolicyIdRef names the policy used to order or prioritize queue items.
  • BudgetDeclRef names the time, compute, cost, risk, or cadence boundary for the planned refresh.
  • RSCRTriggerKindId[] comes from G.Core; scheduling policy does not mint trigger kinds.
  • the plan for refresh is the U.WorkPlan locally called RefreshPlan@Context; executed refresh is recorded in RefreshReport@Context or Work-bound audit.

Use an applicable ordinary queue-order rule when it already settles the scheduling choice. If a needed priority or budget rule is missing, resolve that choice under its governing authority before the plan relies on it; missing required policy pins remain a blocker. A heuristic supplies no policy merely by appearing in a queue.

G.11:5 - Archetypal Grounding — System and Episteme (informative)

U.System illustration — Safety-critical maintenance loop (pump and calibration). A centrifugal pump is serviced under a documented procedure (method description). Sensors report vibration drift (telemetry), and a calibration standard is updated (edition bump). The maintenance team uses G.11 to produce a refresh plan scoped to the affected inspection slices and publishes a refresh report of the executed actions with pins to the updated standard edition and the evidence or source relations. Deprecation notices are issued for obsolete thresholds in the procedure’s acceptance clauses (by subject pattern), preserving ID continuity.

U.Episteme illustration — Living review and benchmark pack (claims and parity). A claim sheet behind a shipped SoTA pack changes (new evidence, retraction, or revised measurement definition). Calibration evidence changes, potentially affecting a bounded-use claim or a justified loss consequence. The maintainers identify which receiving uses depend on the changed row, retain matching results that remain supported, and use the canonical triggers to plan any needed targeted parity rerun. Re-shipping follows only when the publication needs the resulting change; a CL revision alone grants or withdraws no use.

Paired currentness case. A pack’s export-date label changes, but its relied-on claims, source editions, qualification conditions and receiving use remain unchanged and adequately supported by available information. Retain the result; no refresh plan, waiver or no-refresh notice is needed.

In the paired case, a dependency changes so that the shipped benchmark comparison no longer supports use beyond its stated window. Restrict that comparison and retain the warning with the shipped result so a later receiver cannot infer continued comparability. Plan the targeted check or update when it is justified and obtainable; currentness reporting alone does not repair the comparison.

Three bounded currentness cases. These are constructed applications of the same rule.

  • A pump shortlist still consumes the same two immutable method rows, eligibility conditions and source edition. An age alert supplies no changed premise or expired use condition, and the available support remains sufficient for the same triage use. Retain the shortlist; no plan or omission certificate is needed.
  • A local selected-set result consumes PumpReviewBudget-E1. Its replacement PumpReviewBudget-E2 changes the allowed review time from 30 to 20 minutes. The existing result cites that budget; no evidence graph is in use. Scope PumpTriageSelection names that result, changed budget and dependent eligibility comparison. If re-selection is chosen, plan only that comparison through G.5 under PatternScopeId=PumpTriageSelection, carrying both budget editions and the current task/row refs. Record performed refresh and any required targeted check in the resulting report before republication.
  • A shipped QD archive expresses its affected dependencies in PathSliceId=ArchiveCell-Q7. A distance-definition change reopens the comparison using that definition. Retain the slice, old/new DistanceDefRef.edition, descriptor, insertion/emitter and policy pins, and the applicable G.9/G.10 evidence and shipping requirements. An OEE change to TransferRulesRef.edition similarly retains its affected graph slice, exact generator row edition and environment-validity scope. Nongraph support elsewhere does not relax these contracts.

Shared calibration, different branch outcomes. Continue G.6:5.5’s constructed case. A correction to calibration qualification K establishes that its uncertainty statement applies only in the low-vibration condition. P1 and P2 both consume K, and selection S uses their acceptance results; P3 uses another calibration. The complete affected scope includes P1, P2 and S, while P3 retains its independent basis.

The inspection team checks the existing configuration records. The records show that M1 was obtained in the qualified condition, so the applicable measurement and acceptance rules preserve its supported result. M2 was obtained outside that condition; the old uncertainty statement cannot support V2 for the proposed use. Preserve the actual measurement history while returning its changed qualification to C.16 and the acceptance question to G.4.

Reconsider S under G.5 because it consumed V2. A permissible shortlist restricted to the supported candidate can answer the immediate triage question; keeping P1 does not preserve the original two-candidate conclusion.

For a later decision that requires V2, the team compares using a qualified independent measurement already available, obtaining a new calibration or measurement, narrowing the planned use and deferring it.

In this case, an available independent measurement covers the required conditions and its assessment fits the decision window; a full repeat campaign would arrive too late and adds no needed coverage. The team selects assessment of that measurement under the subject rules. If it supports V2, S can be reconsidered with both supported branches. If it does not, retain the warranted restricted result. Record a new observation or performed refresh only when it occurs; the plan and the available measurement remain distinct.

G.11:6 - Bias-Annotation (informative)

  • Arch bias (toward explicit wiring). Risk: authors feel “over-pinned.” Mitigation: keep the minimum pin set small; push scheduling sophistication into extensions and policies.
  • Gov bias (toward audit over speed). Requiring a queue, plan or report for every unchanged result adds paperwork. To avoid it, create queue, plan and report content only for the corresponding need; retain applicable support without an omission certificate, while preserving warnings a later receiver needs.
  • Onto and Epist bias (toward one governing definition for trigger meaning). Risk: teams try to localize trigger meaning for convenience. Mitigation: alias docking is allowed, but semantics stay in G.Core.
  • Prag bias (toward minimal recomputation). Risk: the first affected slice is mistaken for complete reach. Mitigation: follow the shared basis to every dependent use under §4.3.2 and preserve the coverage limits.
  • Did bias (toward readable, reusable artefacts). Risk: an example can hide a condition that matters for another use. Mitigation: recover the receiving question and qualifications of that use before applying the example.

G.11:7 - Conformance Checklist (normative)

IDRequirementPurpose and Notes
CC‑G11‑CoreRefA conforming G.11 artefact MUST satisfy the effective core conformance set implied by the GCoreLinkageManifest in G.11:4.1 (profile expansion plus explicit deltas; delegated to G.Core).G.11 is conformant only if the relevant G.Core invariants and trigger discipline are satisfied.
CC‑G11.1 (Slice-scoped planning).A conforming RefreshPlan@Context SHALL name its complete affected scope as PathSliceId[] (preferred where graph-expressed) or PatternScopeId[] and record canonical RSCRTriggerKindId for each planned cause. Its closure rationale SHALL account for all dependent uses that can change within the declared coverage, including shared-premise branches and combining uses. Pack-wide reruns MAY occur only if that closure spans all slices.Prevents both unrelated reruns and omission of another dependent use.
CC‑G11.2 (Edition discipline; QD and OEE wiring).When QD, OEE, or both are active, a conforming RefreshPlan@Context and RefreshReport@Context SHALL satisfy the required pin, edition, and policy wiring of the applicable extension blocks: G.11:Ext.QDRefreshWiring, G.11:Ext.OEERefreshWiring, or both. .edition SHALL apply only on …Ref. Missing required pins SHALL block publication.Keeps replayability strict while keeping method-specific pin lists inside the applicable extension blocks.
CC‑G11.3 (Telemetry-metric admissibility).A refresh SHALL retain the metrics and pins required by the applicable subject method and receiving contract. Any Q, D, QD-score, coverage or regret it publishes SHALL be published as telemetry metrics, and any published IlluminationSummary as a telemetry summary. These values SHALL be excluded from dominance unless a CAL policy explicitly promotes them, and the promoting policy id SHALL be recorded in SCR-visible evidence bindings through the cited subject patterns.Preserves required telemetry and prevents covert scalarisation.
CC‑G11.4 (Bridge penalties).Any refresh reacting to a sense or kind correspondence change or to a change in an independently governed plane relation SHALL satisfy CC‑GCORE‑PEN‑1. It SHALL preserve the obtaining relation under its direct governor, cited calibration basis and losses, and the separate receiving-use and reliance claims consumed by the refreshed result. It SHALL publish the CL, CL^k, CL^plane values and policy/model pins required by the actual calibration or receiving use, including any required Φ, Ψ and Φ_plane policy ids. Any numerical assurance penalty SHALL satisfy the model applicability and declared-result conditions of CC‑GCORE‑PEN‑1.Keeps the actual relation, calibration and assurance grounds recoverable during refresh.
CC‑G11.5 (Selector invariants).Any orchestrated re‑selection or selected-set or archive update SHALL (i) satisfy CC‑GCORE‑SET‑1 (delegation), and (ii) cite the selector governing definition (G.5) with the comparator admitted for that use at its applicable edition, and preserve the actual declared outcome: the relevant selected-set kind, narrowed handoff, abstention, or escalation. A changed comparator basis must be explicit under its own governor; G.11 introduces no scalarisation or replacement result semantics.Prevents refresh from changing order semantics.
CC‑G11.6 (Crossing visibility).Refresh actions that touch cross-context reuse SHALL satisfy CC‑GCORE‑CROSS‑1 under the obtaining relation’s direct governor, retaining its relation reference and the separate receiving-use and reliance grounds required by that governor. An independently governed E.18 flow crossing or A.21 gate that consumes the refreshed content SHALL retain its required harness, pins, lexical constraints and lane checks. Missing required grounds or pins SHALL block the affected publication.Makes reuse and actual flow crossings or gates checkable under their own requirements.
CC‑G11.7 (Use-qualified currentness).A freshness or decay trigger SHALL be interpreted under B.3.4 for the relied-on claim/use and affected dependencies. Continue on sufficient applicable support without mandatory refresh, deprecation, waiver, WorkPlan or omission certificate. A later receiver SHALL receive the minimum action-changing limitation or reason with the existing result/publication. Publish DeprecationNotice@Context only for actual deprecation; an exception requires actual authority and scope.Preserves useful currentness warnings without treating age as lost assurance or manufacturing a completion artefact.
CC‑G11.8 (No default smuggling).A conforming G.11 refresh artefact SHALL NOT introduce new defaults for PortfolioMode, dominance, Γ-fold, or guard behavior. If orchestrated steps rely on defaults, the artefact SHALL cite each default’s governing definition through G.Core.DefaultGoverningDefinitionIndex and the applicable subject patterns rather than restating defaults inside G.11.Protects default definition-citation discipline under orchestration pressure.
CC‑G11.9 (Targeted RSCR before republication).Before changed refresh content is republished downstream, run or cite the required targeted RSCR or regression check for its affected scope. Keep the reference in the existing result/publication or corresponding RefreshReport@Context. Reuse a current matching result for unchanged content; no new execution report is required solely to repeat that reference. A missing required check retains the applicable degrade or abstain outcome under its governing policy.Keeps actual republication checks while separating their evidence from unnecessary repeated work.
CC-G11.10 (Causal-use refresh sentinels).When a refreshed publication or output consumes C.28, a conforming RefreshPlan@Context SHALL include causal-use sentinel payload distinctions when counterfactual realizability, counterfactual-data identification and bounding, target-trial reporting, causal fairness, causal representation validation, off-policy and causal-RL evaluation, or simulation validation can change supported use, unsupported use, support verdict, assurance, parity, or downstream selection.Keeps moving causal SoTA from silently invalidating shipped causal-use results while preserving G.Core trigger governance.
CC-G11.11 (Relation-derivation dependency refresh).When a reused A.6.RCD predicate definition or admitted derived relation kind depends on base definitions, a named substrate edition, an authorized derivation operation, or an applicability scope, the refresh plan SHALL pin those dependencies and reopen the affected derivation and dependent uses when one changes. The plan uses existing canonical trigger kinds; it does not mint a relation-specific trigger kind.Prevents a once-valid derivation from surviving a changed semantic or substrate basis.

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

Anti-patternSymptomWhy it failsRepair
Full-rerun mania or first-slice stopAn edit reopens every result or only the first located slice.The scope follows storage or discovery order instead of actual dependence.Follow §4.3.2 through every affected branch and combining use; retain independent results and coverage limits (CC‑G11.1).
Editionless telemetryTelemetry lacks …Ref.editionReruns are non-comparable; parity breaksBlock publication on missing pins (CC‑G11.2)
Alias-as-semanticsT* labels are treated as meaningTrigger meaning fragments; regressions become untestableDock aliases through G.Core.TriggerAliasMap.G11; record canonical ids
Silent crossing during refreshCross-context or plane reuse lacks required relation/use/reliance grounds, or an actual flow crossing or gate lacks required visibility pins.The reuse or crossing cannot be checked against its governing rule.Restore the missing grounds; apply E.18/A.21 harnesses to independently governed flow crossings or gates. Block the affected publication when required grounds or pins are missing (CC‑G11.6).
Default smugglingRefresh introduces “helpful” default dominance or PortfolioMode behaviorCompeting defaults appear; downstream arguments driftCite governing definitions through G.Core.DefaultGoverningDefinitionIndex (CC‑G11.8)
Lost currentness warningA later recipient relies beyond the supported condition or window because the changed limitation was omitted.The old result can no longer support that receiving use.Keep the minimum useful warning or decision with the existing result; use a deprecation notice only for actual deprecation. An unchanged immediate use needs no skip-refresh record (CC‑G11.7).

G.11:9 - Consequences (informative)

  • Selective, replayable upkeep. The practitioner can retain a sufficient result or trace selected refresh from its changed premise through dependent uses to performed work and its results.
  • Stable semantics with flexible operations. Trigger meaning is centralized (G.Core), while scheduling sophistication can evolve as policy-bound extensions.
  • Governing definitions. Refresh coordinates actions under their existing rules. For example, G.10 governs shipping and G.5 governs selection.
  • Cost: pin discipline overhead. Authors carry the ids, editions and policies needed to make refresh comparable and to recover its dependencies.

G.11:10 - Rationale (informative)

G.6 makes a cited basis and its paths recoverable; G.11 connects the affected reach to a supported continuation. A shared premise can require several local judgements, while independent results remain usable. The connection separates three concerns:

  • The refresh loop coordinates reruns and republishing; G.Core governs trigger meanings and invariants and identifies the governing definition for each default.
  • The kit is split across the P2W planning-to-work boundary so that the U.WorkPlan and its declaration-local planned-filling rows remain planning content while dated Work remains independently established.
  • Alias stability is maintained by allowing trigger aliases (T0…T7) while prohibiting them from becoming semantic authorities.

G.11:11 - SoTA-Echoing — Post‑2015 practices aligned (informative)

Each entry follows: claim → practice → source → alignment → adoption status.

0. QD currentness requires visible survey support. Practice: current QD work is surveyed as approaches, applications, and challenges, with archive, diversity, descriptor, and evaluator-currentness concerns still live. Source: A survey on Quality-Diversity optimization: Approaches, applications, and challenges, Swarm and Evolutionary Computation 2026, DOI 10.1016/j.swevo.2025.102240. Alignment: RefreshCurrentnessLine@Context may name selected set, Front, Q-front, ExplorationArchive, Archive, portfolio lineage, descriptor or distance edition, and path-slice scope, while C.18, C.19, and G.5 keep archive, pool, and selected-set meanings. Adoption: Adopt and bound (survey support changes refresh currentness fields and boundaries; it is not the governing ontology source).

0a. Open-ended engineering outputs need source and evaluator currentness. Practice: self-improving-agent, AlphaEvolve-style, and DeepEvolve-style lines use generated variants, external knowledge, evaluators, tests, archives, and empirical validation. Source: Darwin Godel Machine arXiv:2505.22954, AlphaEvolve arXiv:2506.13131, and DeepEvolve-style deep-research augmentation arXiv:2510.06056. Alignment: G.11 refresh records carry source, evaluator, descriptor, policy, edition, lineage, and report refs; generated method text, evaluator success, and archive update keep their subject patterns. Adoption: Adopt and adapt (refresh tracks currentness and complete affected scope; generated text, gate passage and performed work retain their different subject claims).

  1. Deployed evaluation needs monitoring and justified refresh conditions. Practice: production ML teams monitor data and model behaviour, relate staleness to prediction quality, and use observed changes to decide when to update. Source: Breck et al., The ML Test Score (IEEE Big Data, 2017), Model 4 and Monitor 4; Amershi et al., Software Engineering for Machine Learning: A Case Study (ICSE-SEIP 2019), §II.B. Alignment: G.11 uses typed causes, edition and policy pins, and the receiving-use comparison in §4.3 to select a replayable response. Adoption: Adopt and adapt the monitoring and update-decision practices to affected-use refresh; retain sufficient applicable support.

  2. Non-stationarity requires explicit drift and decay handling, not ad-hoc updates. Practice: continual learning emphasizes non-stationarity as a first-class maintenance condition. Source: Parisi et al., Continual Lifelong Learning with Neural Networks (arXiv:1802.07569, 2019); De Lange et al., A Continual Learning Survey (arXiv:1909.08383, 2021). Alignment: B.3.4 supplies use-qualified currentness. G.11 interprets changed conditions and justified review signals before planning an affected-scope refresh; elapsed time alone implies neither truth decay nor deprecation. Adoption: Adapt (refresh of conceptual artefacts and evidence closures, not untracked model mutation).

  3. Quality-Diversity requires archive semantics and comparability under descriptor and distance evolution. Practice: QD methods treat the archive as the primary result and track changes under policy and edition conditions. Source: contemporary QD families such as CMA-MAE (arXiv:2205.10752) and differentiable QD (arXiv:2106.03894). Alignment: QD-specific meaning lives with the subject patterns; G.11:Ext.QDRefreshWiring ensures edition pins and scope pins exist so targeted archive refresh is admissible. Adoption: Adopt (set and archive preservation; no covert scalarization).

  4. Open-endedness co-evolves environments and agents; transfer rules must be versioned. Practice: POET-class open-ended systems require explicit transfer rules and environment validity constraints. Source: Wang et al., POET (arXiv:1901.01753, 2019); later generator-family claims require a named G.2 SoTA pack or exact current source. Alignment: G.11:Ext.OEERefreshWiring requires TransferRulesRef.edition and scope pins so refresh reruns remain comparable and auditable. Adoption: Adopt and adapt (adapted to Part G pin and UTS publication discipline).

  5. Efficient orchestration benefits from bandit and early-stopping scheduling, but scheduling must not redefine trigger, action, parity, shipping, or Part-G-wide default semantics. Practice: modern hyperparameter and experiment scheduling uses bandit-style resource allocation and asynchronous early stopping. Source: ASHA (arXiv:1810.05934) and BOHB (arXiv:1807.01774) as representative post-2015 scheduling practice. Alignment: scheduling is expressed as RefreshQueue and RefreshPlan@Context policy pins (RefreshPriorityPolicyIdRef, BudgetDeclRef) so core semantics remain stable and the U.WorkPlan stays separate from dated Work. Adoption: Adapt (useful practice, but quarantined outside core norms).

G.11:12 - Relations

Builds on: G.Core (Part‑G invariants; RSCR trigger catalogue; alias docking; Default Governing Definition Index), G.6 (EvidenceGraph, PathId and PathSliceId), G.7 (Bridge sentinels; CL, Φ, and plane pins), G.5 (selector and set-return), G.8 (bundle telemetry hooks), G.9 (parity), G.10 (shipping hooks), B.3.4 (freshness and decay), E.18 (GateCrossing visibility).

Coordinates with: A.10.1 for source-change discovery, direct-use tests and affected reach; C.11.DUA for choosing worthwhile inquiry or a sufficient present answer; G.12 for dashboard telemetry pins; A.6.RCD for reopening reused predicate definitions and derived relation kinds when their base definitions, named substrate edition, authorized derivation operation or applicability changes; C.18 and C.19 for archive, front and live-pool policy pins; C.32.P2S when telemetry, decay or freshness reopens architecture problem-to-structure carry-through; C.23 for SoS-LOG branches and maturity ladders; C.28 for causal-use support results, verdicts, supported and unsupported uses, and causal-use sentinel payloads; F.15 for RSCR harness publications when present.

Publishes to: UTS (refresh plan, refresh report, deprecations, edition bumps), and to the relevant subject patterns’ publication faces, forms, or units through delegated actions.

G.11:End

Referenced in the corpus

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