E.18.1:4.1 - Compact carry-through episteme (conditional reliance extension)

Open this extension only when transfer, audit, delayed feedback, expensive reversal, automation, or durable reuse requires someone to replay the stable P2W core. Materialize one ordinary C.2.1 episteme whose exact EntityOfConcern is the accepted ProblemCard@Context, whose ClaimContent is the current positive or stopped carry-through account, and whose effective ReferenceScheme governs its designations. Carry-through note and stop description are Plain use labels for those two ClaimContent shapes, not local U-kinds or relation species.

carryThroughClaimContent:
  acceptedProblemCardEditionRef
  carriedProblemCardClaimSlice
  receivingDecisionOrUse
  nextPracticalQuestion
  applicablePatternRef: pattern whose Solution answers nextPracticalQuestion
  contributionUsed: particular definition, admission, selection, method, decision rule, publication rule, returned result, or other concrete contribution used in this case
  returnedResultKindRef?: exact kind returned by that pattern
  returnedResultRef?: exact positive result, relation occurrence, assertion or description
  honestStop?: exact blocker or reduced-use cue returned by that pattern
  carryThroughRationale
  localNonOverread?
  precedingCarryThroughEpistemeRef?: replay/source pointer only, with an exact relation when continuity or derivation is claimed
  continuationDescriptions[]: one question or use, applicable pattern reference, and particular contribution used per continuation
  returnCondition?

A positive use fills the exact returned result and leaves honestStop absent. A stopped use fills the returned blocker or reduced-use cue and fabricates no positive result. When the claim uses a separately identified U.Viewpoint episteme or BoundedModelUseStructure and that object’s organization changes how the receiving claim is interpreted, the ClaimContent designates it; otherwise no surrogate field is filled. Citing a PatternID does not thereby admit a U.MethodDescription. The episteme, its claim and its predecessor pointer are neither a reusable predicate definition nor a P2W relation kind or occurrence.

A positive use is well formed only when the named result kind is one that the cited pattern actually returns for the stated question, the carried ClaimGraph content remains relevant to the receiving use, and every independent continuation stays separate. When the result is a relation occurrence, assertion, or description, cite that exact object; keep its obtaining or claim basis, occurrence-identity rule, and any receiver-conditioned reusable declaration or typed SlotSpecs with that returned object under the pattern content that defined or tested it. A predecessor pointer supports replay only and establishes neither episteme continuity nor another occurrence.

For first-minute use, state the question, apply the pattern that answers it, and continue with its result or stop without materializing this episteme. Materialize it only when replay is required. Each continuation names one applicable pattern reference and one question or use that its result answers. Do not combine value kind and relation signature, method and mechanism, evidence and assurance, plan and dated Work, actual Transformation and production, or refresh and residual triage in one field.

The use closes positively when the cited pattern has returned its positive result and the carried problem-card claim remains visible in that result or its stated basis. It closes by bounded stop when the cited pattern returns a blocker or reduced-use cue and no positive continuation can be stated.