E.18.1:4.8 - Conditional reliance replay after a relied-on value changes

Open this extension only when transfer, audit, delayed feedback, costly reversal, automation, or durable reuse requires a durable account of what still follows after source-currentness repair, appearance-based reliance repair, changed measurement, changed problem-side record, FPF pattern change, or a use-found defect. An ordinary local return uses 4.5 and creates no replay episteme.

Materialize one ordinary C.2.1 episteme whose EntityOfConcern is the accepted ProblemCard carried by the original carry-through episteme, whose ClaimContent is the replay account below, and whose effective ReferenceScheme governs its designations. Replay note is Plain wording for this use, not a local U-kind, refresh process, change log or authority record.

replayClaimContent:
  originalCarryThroughEpistemeRef
  changedValueRef
  changedValueKindRef
  changedValuePatternRef: pattern containing the guidance applied in the earlier use of changedValueRef
  changedValueContributionUsed: exact Solution passage applied in that earlier use
  stillCarriedClaimSlice
  noLongerCarriedClaimSlice?
  smallestReopenedContinuation
  refreshCurrentnessLineRef?: exact current G.11 episteme or relation
  nextApplicablePatternRef: pattern whose Solution answers the reopened question

Reapply the exact guidance recorded for the earlier use before filling the replay episteme, then use the basis it supplied or located with current facts to reassess the earlier claim or result about the independently identified changed value. If the changed object is a relation, that reassessment first judges whether the relation obtains; apply A.6.REL afterward only when relation-occurrence identity is current. The earlier result keeps its participants, obtaining or claim basis, occurrence-identity rule and any reusable RelationSignature or typed SlotSpecs. The replay account records only what still follows, what no longer follows and which P2W continuation reopens. Citing a PatternID does not admit a MethodDescription.

P2W may cite a readable relation assertion, an explicitly individuated occurrence, or a typed assertion or description, but it cites the independently identified object that served as the earlier result together with its obtaining or claim basis. Citation does not make relation use signature-dependent; a receiving episteme carries a signature reference only when the defining content for that exact claim requires one.

The changed object may instead be a source edition, measurement, unit, reference plane, Method set, comparator, module-interface relation, publication-use relation, problem record, or FPF pattern publication. Whatever changed keeps its own kind. If the reopened use depends on maintenance, responsibility, or authority, name the direct relation and its participants; an owner-shaped label is not enough. Reapply the guidance used for the earlier result. Add a G.11 line only when one exists. The practitioner or another capable system applies the guidance to the reopened question and decides whether to continue, stop, split, retain a reduced-use cue, or return upstream.