A.6.3.CR:4.3 - Working-model first; explicit review record only when the case needs fuller review

Follow E.14’s working-model-first discipline: an ordinary report, summary, or translation states what stayed the same, what was omitted, when the rewrite stops being conservative, and which pattern to use next. Put only the support needed for the current review or reliance question beneath that account.

Ordinary case (default). For everyday entityOfConcernRef-preserving rewrites, it is usually enough that the text or its surrounding publication keeps explicit:

• which source U.Episteme claims are being re-expressed;
• that the EntityOfConcern resolved by each side’s entityOfConcernRef remains the same;
• whether the case is direct or correspondence-mediated when that is not obvious;
• what omissions or source-loss modes matter for the reader;
• which pattern to use if the case becomes explanation, representation shift, retargeting, gate, evidence, work, assurance, Bridge use, or another non-retextualization claim.

Explicit review record (when fuller review is needed). A fuller record is warranted when the case is assurance-facing, gate-adjacent, cross-context, correspondence-heavy, policy-bearing, or likely to be disputed. Include or inherit the fields needed to inspect the material preservation, correspondence, source-use, or downstream-use question. The record may inherit pattern ids and already-pinned metadata instead of restating them inline. The available field groups are:

• transform relation (patternSpecializationRef = A.6.3 specialization, relationFunctionClaimRef, sourcePublicationOrRecordForm, targetPublicationOrRecordForm, changeTargetRef);
• preservation context (entityOfConcernPolicy = preserve, boundedContextPolicy, viewpointPolicy, referenceSchemePolicy, representationSchemePolicy, groundingPolicy, referencePlanePolicy);
• claim and publication discipline (claimPolicy, claimScopePolicy, publicationScopePolicy, reliabilityTransportPolicy, pinningPolicy, provenancePolicy, lossProfile);
• continuity and bridge discipline (claimContinuityClass, microtheoryContinuityClass, onticContinuityClass, bridgeRequirement, conservativityWitness);
• downstream and admissibility discipline (worldContactPolicy, evidencePolicy, gatePolicy, workCrossing, upstreamPatternLocator, downstreamPatternLocator, admissibleFaces, admissiblePublicationRenderings, compositionRule, reopenCondition);
• naming and presentation discipline (publicNamePolicy).

The fuller record makes these cases reviewable without hiding meaning in style, topic familiarity, or editor intuition.