A.6.3.CR - ConservativeRetextualization: EntityOfConcern-Preserving Textual Re-Expression

Type: Specialization pattern Status: Stable Normativity: Normative

A.6.3.CR:1 - Problem frame

Use this pattern when one already available source line about the same EntityOfConcern needs a second textual form: a report rewrite, summary, translation, or declared filtered restatement. The real job is still same-entity textual re-expression, not explanation, representation change, bridge work, retargeting, evidence, gate authority, or work authorization.

Primary governed case. One textual re-expression of already available source claims whose resolved EntityOfConcern remains the same. The source and receiving epistemes concern that entity; the textual rendering expresses the receiving claims.

First useful move. Separate the source slice, the published slice, the omission or source-loss note, and the admissible use. If preservation is doubtful, name the missing basis or defect; repair it within CR when possible, or name the pattern for the actual changed claim or use.

What goes wrong if missed. A summary, translation, or manager-readable rewrite is treated as harmless editing after it has started hiding explanation work, bridge work, changed authority relation, or a narrower admissible use.

What this buys. One honest same-entity textual rewrite with visible source-relation tether, visible omission or loss notes, and a clear repair or next-pattern route when conservativity fails.

Ordinary use. If the rewrite is admissible only for orientation, source-finding, review, comparison, or planning preparation, one source-slice to published-slice sentence or mini-card with the admissible use and visible omission or source-loss note is enough.

Reliance-facing use. Open the fuller rewrite-admissibility record only when the rewritten text will be externally relied on, disputed, cited as a source-relation reason, used across context, or read as release, gate, work-preparation, engineering-justification, approval, or evidence justification.

Not this pattern when. Not this pattern when the case is primarily explanatory rendering (ExplanationFaithfulnessProfile), representation-scheme change (RepresentationSchemeTransition), changed EntityOfConcern (A.6.4), comparative review (E.17.ID.CR), an F.9 Bridge or bounded-use claim, an optional F.9.1 stance note about such a claim, or a deliberately coarsened rendering whose narrower admissible use, non-admissible downstream use, and source-bearing return have become primary. In that last case, use A.6.3.CSC Controlled Semantic Coarsening.

A.6.3.CR:2 - Problem

Without a dedicated pattern for conservative textual re-expression:

1. report, summary, translation, and filtered rewrite cases are handled ad hoc;
2. authors treat textual simplification as if it were automatically conservative;
3. the boundary to explanation-facing renderings stays blurry;
4. correspondence-mediated rewrites are not distinguished from direct rewrites;
5. subsequent users cannot tell whether the result is still a view of the same EntityOfConcern or a new interpretive publication.

A.6.3.CR:3 - Forces

• Same entity, different wording. Readers need different textual forms without reopening the EntityOfConcern.
• Compression vs loss visibility. Shorter or plainer forms are often useful, but omissions and source-loss modes must stay explicit.
• Direct vs correspondence-mediated rewrites. Some rewrites read from one source episteme; others depend on a declared CorrespondenceModel.
• Textual focus vs family creep. The pattern should cover same-entity textual re-expression, not explanation, not representation-wide shifts, and not retargeting.
• Publication discipline. Admissible MVPK faces and publication renderings still matter even when the transform looks like “just a rewrite.”

A.6.3.CR:4 - Solution — entityOfConcernRef-preserving textual re-expression under A.6.3

A.6.3.CR:4.1 - Informal definition

ConservativeRetextualization is a named pattern specialized under A.6.3 U.EpistemicViewing for textual re-expression of the same EntityOfConcern.

It preserves the exact EntityOfConcern resolved by each side’s entityOfConcernRef under that side’s effective ReferenceScheme, keeps the transform effect-free, and allows only claim-preserving or explicitly loss-declared rewriting of already available content.

It may change register, ordering, textual density, language, emphasis, or local wording. It may not silently introduce new claims, an F.9 Bridge, bounded-use suitability, current reliance, authorization, actual receiving use, new Work, evidence, gate, release, policy, assurance, adjudication force, or a changed EntityOfConcern.

Here, entityOfConcernRef-preserving means that resolved-entity equality, not identical reference spelling. Keep a material reference or scheme change explicit under A.6.3:4.3.

A.6.3.CR:4.1.a - Pattern, case, and publication distinction

ConservativeRetextualization is a pattern description and a named specialization under A.6.3. Concrete entityOfConcernRef-preserving rewrites are passive episteme cases or publication texts reviewed under this pattern.

This distinction matters because the pattern defines or constrains how a rewrite is recognised, justified, and checked.

A.6.3.CR:4.1.b - Local working vocabulary

This pattern repeatedly uses a small working vocabulary.

• Source slice = the already available pinned or otherwise reviewable textual content being restated.
• Published slice = the resulting textual rendering that remains under entityOfConcernRef-preserving discipline.
• Ordinary case = a reviewable same-entity rewrite where a short account keeps the source tether, omission notes, and neighboring-pattern conditions readable.
• Case needing fuller review = a case where dispute, policy, assurance, required correspondence witness, or cross-context reliance makes a fuller record worth publishing.

sourceSlice and publishedSlice are local review labels for the source textual slice and resulting textual rendering in one rewrite case. A publishedSlice remains a rendering label. When one exact selected U.Episteme is made available, E.24.PUB separately requires its bounded-use declaration, publication form, carrier, and obtaining EpistemePublicationRelation; no publication kind or second episteme identity follows from the slice label.

These local review labels follow the E.17:5.1e local-field rule.

A.6.3.CR:4.2 - Scope and exclusions

In scope

• entityOfConcernRef-preserving report rewrite;
• entityOfConcernRef-preserving summary;
• entityOfConcernRef-preserving translation between natural-language textual forms;
• declared filtering or foregrounding of already-present claims in textual form.
• correspondence-witnessed textual synthesis where every receiving claim remains recoverable to one entityOfConcernRef-preserving source line or declared entityOfConcernRef-preserving correspondence witness.

Out of scope

• a difference between the EntityOfConcern values resolved by the source and receiving references, including a hidden change of EntityOfConcern (A.6.4);
• explanation-facing renderings whose main purpose is explanatory rendering rather than same-entity rewrite (ExplanationFaithfulnessProfile);
• representation-regime changes such as text→table, text→diagram, or text→latent form (RepresentationSchemeTransition);
• comparison, abductive-prompt, ranking, recommendation, bridge-mediated, substitution, or action-selection work that introduces new claims rather than restating available ones.

A.6.3.CR:4.2.a - Reader guidance

Use this pattern when the EntityOfConcern stays fixed and textual restatement remains the primary move.

• If the main change is explanatory, apply ExplanationFaithfulnessProfile.
• If the main change is a representation-scheme shift, apply RepresentationSchemeTransition.
• If the EntityOfConcern changes, apply A.6.4.

A.6.3.CR:4.2.b - What the user checks first

The user usually does not begin by filling every field name. The first useful questions are simpler:

1. Is the published result still about the same EntityOfConcern?
2. Does the result remain a textual restatement, or is explanation or a representation-scheme change now primary?
3. Can the reader see what was omitted, softened, or foregrounded?
4. If several source slices or a correspondence witness are doing work, can each receiving claim be traced to one entityOfConcernRef-preserving source line or declared entityOfConcernRef-preserving correspondence witness?
5. Is the source merely pointed at, was it actually used, are the rewritten claims recoverable from it, and is the result admissible for the intended use?
6. If any answer is doubtful, is the problem a missing source or condition, a repairable preservation defect, or an actual changed claim needing another pattern?

If omissions, softening, or filtering are admissible only because the published result is coarsened, tied to narrower admissible use, non-admissible for downstream use, and tied to source-bearing return, the case has crossed out of ordinary conservative retextualization even if the prose still looks like a summary. Use A.6.3.CSC Controlled Semantic Coarsening for that source-to-rendering relation.

Here, source-bearing return means returning to the source-bearing content. First identify any missing source or condition and repair and recheck a preservation defect within CR when the intended restatement can be restored. A changed-claim exit applies when the attempted claim really becomes explanation, representation shift, retargeting, gate, evidence, Work, assurance, or Bridge use: name that claim and use the pattern that defines, constrains, or tests it. Resolve the exact predicate or defining ClaimGraph only when the current claim or a named later use depends on that rule edition. A coarsened textual slice may need both source-bearing return and a changed-claim exit.

Only after these questions are answered does a fuller review record usually become worth writing.

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.

A.6.3.CR:4.3.a - Ordinary admissibility defaults

Default admissibility for ordinary entityOfConcernRef-preserving textual cases:

• primary admissible faces are PlainView and TechCard;
• bounded report-only use is admissible when source pins, provenance, loss notes, and entityOfConcernRef-preserving conservativity remain visible;
• InteropCard use is admissible only when the governing publication-face source explicitly permits source-pinned, text-preserving export without added semantics;
• AssuranceLane or gate-bearing use is not default and requires governing publication-face policy plus source-pinned conservativity without hidden strengthening.

A.6.3.CR:4.4 - Direct and correspondence-mediated profiles

Direct ConservativeRetextualization

• source slice and published slice are textual re-expressions of one source episteme;
• no CorrespondenceModelRef is needed;
• the main required admissibility record is explicit loss and provenance discipline.

CorrespondenceConservativeRetextualization

• the receiving textual rendering is derived from a declared correspondence between epistemes or views of the same EntityOfConcern;
• CorrespondenceModelRef is required;
• the result remains under A.6.3 only if the correspondence witnesses entityOfConcernRef-preserving conservativity and no new claims are imported beyond the declared witness set.

Cross-language translation is not automatically direct. If the translation depends on declared correspondence, reference-scheme mediation, or bounded equivalence notes, it must be treated as correspondence-mediated rather than disguised direct rewriting.

A.6.3.CR:4.4.a - Recurring same-entity textual moves

The pattern covers a small family of recurring textual moves as long as the same EntityOfConcern remains explicit:

• Register shift — a technical statement is rewritten into plainer engineer-manager prose without changing what is being said about the same entity.
• Summary or filtered restatement — a source note is shortened or focused on one declared slice, with omissions stated rather than hidden.
• Cross-language restatement — the same source claim is restated in another natural language while the same source tether and same-entity line remain explicit.
• Correspondence-witnessed textual synthesis — one textual rendering is produced from declared same-entity correspondences without importing an extra bridge or substitution admissibility record.

These are recurring move shapes, not separate patterns. The specialization relation remains the same: entityOfConcernRef-preserving textual re-expression under A.6.3.

A.6.3.CR:4.5 - Shared conservative retextualization rule bundle

A.6.3.CR:4.5.a. Preservation rule

A case under ConservativeRetextualization preserves the same resolved EntityOfConcern, the declared bounded context, and the already available claim-bearing source while changing wording, register, language, ordering, or density. It states what remains preserved about claim scope, publication scope, pins, provenance, grounding, and ontic scaffold, and it says whether the case is Direct or Correspondence.

A.6.3.CR:4.5.b. Loss and reliability rule

A reviewed case makes explicit what is omitted, shortened, foregrounded, or carried only through a declared source-loss mode by the rewrite. Reliability transport may remain source-bounded or be explicitly downgraded, but it must never be silently widened by cleaner prose, more forceful rhetoric, or management-facing polish.

A.6.3.CR:4.5.c. Authority and changed-claim boundary

A case reviewed under this pattern stays about the same entity and remains an episteme-to-episteme textual rewrite. It does not establish explanation faithfulness, an F.9 Bridge or bounded-use suitability, retargeting, current reliance, authorization, or actual receiving use. If the rewrite becomes explanatory, Bridge-bearing, gate-bearing, or world-facing, state the attempted claim and use the pattern that defines, constrains, or tests it. Use F.9 for a semantic Bridge between two exact F.17 local senses or a proposed bounded use of that Bridge. Take a current reliance question to triggered A.10 or B.3 and authorization to the pattern that directly constrains the receiving act. For an asserted occurrence, first recover the actual object or occurrence under its direct obtaining or admission rule, then cite the evidence on which the assertion relies. A precise dated Work claim needs A.13 and independent A.15.1 admission; add F.6 only for precise assignment-bound attribution. Do not create those records when their branches are not live.

A.6.3.CR:4.5.d. Composition and reopen rule

Repeated direct rewrite over the same source line may be idempotent, but heterogeneous rewrites and correspondence-mediated rewrites are generally order-sensitive. A reviewed case must reopen whenever correspondence witness, source pins, provenance, admissible-face assumptions, or entityOfConcernRef-preserving conservativity stop being explicit. Revalidate the affected claims when a load-bearing source, correspondence witness, provenance, face or use assumption, or preservation condition changes, even if it remains explicit; use E.17:5.1b–c for the applicable reopen condition.

A.6.3.CR:4.5.e. Non-collapse note for correspondence

Correspondence-mediated retextualization does not by itself establish an F.9 Bridge, bounded-use suitability, current reliance, authorization, or actual receiving use. Apply F.9 when a cross-local-sense semantic Bridge or a proposed bounded use of that Bridge is claimed. When reliance is current, apply triggered A.10 or B.3. The pattern for the receiving act handles authorization; recover any asserted occurrence under its direct obtaining or admission rule and cite evidence when the assertion relies on it. These are independent questions, not a mandatory record bundle for every rewrite.

A.6.3.CR:4.5.f. Local conservativity witness for borderline textual cases

For borderline textual rewrites, the user treats the case as conservative only while each point below remains visibly preserved or its loss is declared and admissible for the stated use. A missing basis or repairable defect follows the repair route in §4.2.b; an actual changed claim or use follows the pattern that defines, constrains, or tests it.

• Modality and force. A rewrite may not silently turn possibility, uncertainty, permission, obligation, recommendation, decision status, bounded scope, temporal window, or hypothesis language into a wider commitment.
• Caveats and qualifications. A rewrite may not quietly remove conditions, exception notes, uncertainty markers, or temporal qualifiers that still matter for interpreting the same source.
• Reliability assessment. Cleaner prose, better ordering, or manager-facing polish may not silently raise confidence, warrant claim, or readiness for action.
• Bridge and receiving-use boundary. Same-entity textual fluency may not establish a semantic Bridge between local senses, bounded-use suitability, current reliance, authorization, or a comparative-review occurrence. Open only the F.9, A.10 or B.3, authorization, or occurrence branch that the actual later use needs; recover an asserted occurrence under its direct obtaining or admission rule.
• Alternative preservation. A rewrite may not collapse open alternatives, rival hypotheses, or declared plurality into one apparently settled interpretation unless the loss is stated and still admissible under this pattern.

This witness is local to ConservativeRetextualization. It does not replace the broader conservativity invariants of A.6.3; it makes them inspectable for textual rewrites where fluent prose can otherwise hide strengthening.

A.6.3.CR:5 - Archetypal Grounding

A.6.3.CR:5.1 - Same-EntityOfConcern report rewrite

Source note slice. Service S exceeded the latency threshold in the evening batch window. Trace T-44 and dashboard pin D-17 show the spike. Two low-confidence hypotheses remain open.

Published report slice. Evening-batch latency for Service S exceeded the threshold. Source pins: Trace T-44, Dashboard D-17. Low-confidence hypotheses are omitted here and remain in the pinned source note.

This is an admissible direct ConservativeRetextualization because the EntityOfConcern stays fixed, the report remains textual, and the omission is stated rather than hidden. In ordinary internal use, this often needs only source pins plus visible omission notes rather than a full explicit review record.

A.6.3.CR:5.1.a - Ordinary inherited-pin summary

Pinned source cluster. In this example, N-14 is the source note in §5.1; N-14, trace T-44, and dashboard card D-17 are already published together under one incident review bundle.

Published stand-up slice. Evening-batch latency exceeded the threshold for Service S. See N-14 / T-44 / D-17 for the pinned source cluster.

This is still an admissible ordinary case even though the short stand-up slice does not restate every pin and qualifier inline. The didactic point is that lightweight use may inherit already-published pins and provenance when the tether stays visible to the reader.

A.6.3.CR:5.1.b - Benign omission that stays ordinary

Source note slice. Service S exceeded the latency threshold in the evening batch window. Trace T-44 and dashboard pin D-17 show the spike. The note also lists two low-confidence hypotheses for separate investigation.

Published stand-up slice. Evening-batch latency for Service S exceeded the threshold. Source pins: T-44, D-17. Low-confidence hypotheses are omitted from this stand-up note and remain in the pinned source.

This stays ordinary ConservativeRetextualization because the omission is declared, the same EntityOfConcern remains visible, and no separate narrower admissible use, non-admissible downstream use, or source-bearing return is needed to justify the omission. Ordinary omission alone is not controlled semantic coarsening.

A.6.3.CR:5.1.c - Functional-description textual summary

Source note slice. The principle scheme says: choose method family MF-2 for small-batch mixing when material X remains below threshold T; selected method M-2 still requires work plan WP-17 and result measurement RM-4.

Published summary slice. For small-batch mixing, choose method family MF-2 when material X remains below T. Selected method M-2 still requires work plan WP-17 and result measurement RM-4.

This remains ConservativeRetextualization because it is a textual restatement of the same source-episteme claims and it keeps the work-planning and result-measurement requirements visible. It is admissible for interpretation and source-finding. It does not by itself provide performed U.Work, evidence, gate passage, engineering justification, or control architecture. If the summary drops WP-17 or RM-4, or makes the selected method look executable by summary alone, restore those requirements before presenting it as a faithful summary or executable guidance. A deliberately coarsened version needs A.6.3.CSC Controlled Semantic Coarsening with narrower admissible use, forbidden stronger use, and source-bearing return. For stronger use, apply the exact governing requirement to the current facts; the CSC label or a reference alone does not satisfy it.

A.6.3.CR:5.1.d - Generated-summary source-relation variant

A generated or machine-assisted summary may stay in ConservativeRetextualization only when it remains an entityOfConcernRef-preserving textual re-expression and its source relation is visible enough for the intended use. This is the ordinary LLM-generated-summary case: a model-produced paragraph over a pinned inspection note, method-selection note, safety note, incident note, or other source slice is not automatically ExplanationFaithfulnessProfile merely because it was generated; it remains ConservativeRetextualization only while it restates source claims and leaves omissions, loss, and non-admissible uses visible. Ordinary source-finding use can stay light; use the compact variant below when the summary will be reused, cited, disputed, or relied on.

When the generated-summary case needs shared vocabulary, use only the E.17:5.1b source-relation or bounded-use distinction that changes the present use. Keep claim recoverability from the source separate from admissibility for that use, and an unknown relation separate from one known absent. The same source governs independent-verification claims and reopen conditions.

The summary may expose or cite the source slice it restates. It does not become that source slice by fluency, brevity, translation, layout, generated form, or reuse. If the needed source content, governing requirement, or case relation is missing, a repair request or source-gap note is only prospective: it neither establishes earlier source use nor supplies the missing claim support or use condition.

If the generated summary is source-pointer-only, merely plausible, claim-widened, or carrying added linkage, do not treat it as a conservative source-equivalent summary. For source-finding or orientation, retain only the justified pointer and separate any unsupported or new proposition from the source-backed account. Repair the claim against the source, or apply A.6.3.CSC, ExplanationFaithfulnessProfile, RepresentationSchemeTransition, E.17.ID.CR, A.15, A.10, or another pattern that defines, constrains, or tests the actual claim. An orientation or coarsening label alone does not make an unsupported claim source-faithful.

A.6.3.CR:5.2 - Same-EntityOfConcern rewrite via declared correspondence

Source design slice. Cooling loop CL-2 preserves safe temperature margins during standard operating demand.

Source safety slice. Cooling loop CL-2 maintains the temperature condition required for hazard-control claim HC-7 during standard operating demand.

Published joint-review slice. For standard operating demand, Cooling loop CL-2 is described in both the design and safety views as maintaining the required temperature condition. This summary relies on CorrespondenceModel CM-12 and does not add claims beyond that declared overlap.

The synthesis may stay in this pattern only if the source relation remains explicit, every downstream claim remains recoverable to the design slice, the safety slice, or the declared CorrespondenceModel, and the text does not silently widen claims beyond the declared entityOfConcernRef-preserving overlap. Because this case requires a correspondence witness, a fuller review record is usually warranted.

A.6.3.CR:5.2.b - Cross-language re-expression without hidden bridge work

Source slice. The backup controller stays in passive watch mode until the primary loop fails two consecutive heartbeat checks.

Published slice. Резервный контроллер остаётся в режиме пассивного наблюдения, пока основной контур не провалит две последовательные проверки heartbeat.

English reader gloss (comprehension aid only). The backup controller remains in passive observation mode until the primary loop fails two consecutive heartbeat checks.

The gloss helps an English-only reader follow the example and find the claim being re-expressed. It is a comprehension aid, not a second source or verification of the Russian translation. A conservativity claim still requires suitable language competence or other evidence for the same-claim, same-EntityOfConcern, and hidden-bridge tests.

This remains in ConservativeRetextualization only if the translation is tethered to the same source claim, preserves the same EntityOfConcern, and adds no claim beyond the source. Apply F.9 only when a semantic Bridge between local senses or a proposed bounded use of that Bridge is claimed.

A.6.3.CR:5.2.c - Boundary to controlled coarsening

Source slice. Vendor bulletin VB-7 requires rollback when pressure drift exceeds 2.5%, and it keeps two equipment-specific exceptions in the pinned annex.

Published coarsened slice. Pressure drift above 2.5% is a warning condition in the bulletin. Check the pinned bulletin and annex before treating the note as rollback guidance.

This does not remain ordinary ConservativeRetextualization. The coarsened slice drops equipment-specific exceptions and remains only an orientation warning: it is not an executable rollback command. It can stay honest only through narrower admissible use, non-admissible downstream use, and source-bearing return to the source-bearing bulletin. Once that narrower-use boundary becomes primary, the case leaves ordinary same-entity rewrite and must use A.6.3.CSC Controlled Semantic Coarsening rather than being treated as a harmless summary.

A.6.3.CR:5.3 - Boundary to explanation-facing renderings

A text is rewritten not mainly to restate the same source, but to explain why it matters, simplify reasoning for a learner, or narrate a mechanism. That move should leave ConservativeRetextualization and be reviewed under ExplanationFaithfulnessProfile.

A.6.3.CR:5.4 - Boundary to representation-scheme transition

A prose note is rewritten as a table, matrix, diagram, latent representation, or distributed representation with a material representation-scheme change. Even if the EntityOfConcern stays fixed, this is not only a textual rewrite; it belongs with RepresentationSchemeTransition.

A.6.3.CR:6 - Bias-Annotation

This pattern intentionally biases toward same-entity conservativity and away from explanation or retargeting inflation. The main mitigation is to repair a preservation defect within CR when possible and apply ExplanationFaithfulnessProfile, RepresentationSchemeTransition, A.6.4, or the pattern that defines, constrains, or tests the actual changed claim or use when it requires leaving same-entity textual restatement.

A.6.3.CR:7 - Conformance Checklist

1. CC-CR-1 — Same EntityOfConcern remains explicit. The EntityOfConcern values independently resolved by the source and receiving entityOfConcernRef values are equal.
2. CC-CR-2 — Textual re-expression remains the right family. Textual restatement remains primary; explanation or a material representation-scheme change is not the primary move.
3. CC-CR-3 — Loss, provenance, pinning, and reliability are explicit or inherited by pinned reference. The case states these explicitly or inherits them through already-pinned content that remains visible to review.
4. CC-CR-4 — Direct vs correspondence split is explicit. The direct-vs-correspondence split is explicit and justified.
5. CC-CR-5 — Correspondence witness is named where needed. If correspondence-mediated, CorrespondenceModelRef is declared.
6. CC-CR-6 — Local conservativity witness remains satisfied. The reviewed case does not silently widen modality, remove caveats, raise reliability assessment, add an F.9 Bridge or bounded-use suitability claim, establish current reliance or authorization, claim that receiving use occurred, or collapse declared alternatives beyond stated loss notes.
7. CC-CR-7 — A missing condition, preservation defect, or changed claim is explicit on failure. If the case fails a check, name the missing source or condition, the repairable preservation defect, or the actual changed claim. Repair and recheck within CR when the intended restatement can be restored. For an actual different claim or use, name the pattern to use next (ExplanationFaithfulnessProfile, RepresentationSchemeTransition, A.6.4, B.5.2, or another applicable pattern).
8. CC-CR-8 — Working-model first remains intact. Ordinary same-entity rewrites stay lightweight; fuller explicit review records carry the fields needed for cases requiring fuller review.

A.6.3.CR:8 - Common Anti-Patterns and How to Avoid Them

A.6.3.CR:9 - Consequences

• Textual same-entity rewrites get an admissible place without inventing a second pattern for the same move.
• Direct and correspondence-mediated variants stay visibly separated.
• Loss, provenance, and reliability transport become explicit instead of implicit editorial judgement.
• Ordinary working-model use stays lightweight, while cases needing fuller review get the additional record content their risk and use warrant.
• The pattern remains bounded by A.6.3, A.6.4, explanation-facing work, and representation-shift work.

A.6.3.CR:10 - Rationale

This pattern is worth splitting out because same-entity textual re-expression is common and useful. Keeping it under A.6.3 as a named specialization keeps the boundary with neighboring transform families visible, makes a recurring authoring move easier to review, and preserves E.14’s working-model-first discipline for ordinary cases.

A.6.3.CR:11 - SoTA Alignment: Adopted Invariants, Adapted Invariants, and Rejected Shortcuts

SoTA alignment rule. Read each row here as source idea -> local FPF invariant -> practical local test -> popular shortcut rejected. A source citation governs nothing by reputation; it counts only when the cited idea is translated into the Solution, conformance checks, boundary rules, worked slices, and Relations of this pattern.

Traditions covered. This pattern binds itself to architecture-description governance, summarization factuality, translation-quality governance, and plain-language rewrite practice.

Architecture-description governance. A.6.3.CR adopts the discipline that rendered text must stay visibly tied to a declared source publication or U.View line. It therefore rejects same-topic textual polish as sufficient evidence of entityOfConcernRef-preserving conservativity.

Summarization factuality. A.6.3.CR adapts modern factuality concerns into source-sensitive conservativity checking, including independent verification and reopening when those questions are live. Use E.17:5.1b for the source-relation and bounded-use distinctions needed by the case, keeping source recoverability separate from use admissibility; use E.17:5.1c for the shared use-boundary terms and E.17:5.1d to select the primary boundary. This pattern uses them only for entityOfConcernRef-preserving textual restatement.

Translation and plain-language traditions. A.6.3.CR adopts the reader-oriented value of translation and plain rewrite, but rejects the still-popular habit of treating cross-language or plain-language textual fluency as automatic proof that no new claim has been introduced. The W3C MQM source is used for issue-type and evaluation discipline, not as a brand-level warrant that a translated or rewritten sentence is source-equivalent.

Local stance. Best-known current practice motivates a narrow rule: entityOfConcernRef-preserving textual restatement is admissible only when source tether, loss, provenance, and same-entity bounds remain explicit enough that the reader can still tell what was preserved, what was omitted, when the rewrite has become a different claim, and which pattern to use next.

A.6.3.CR:12 - Relations

• Builds on: A.6.3, A.6.2, A.7, E.10.D2, E.17.0, E.17, F.9, F.18, E.10
• Coordinates with: ExplanationFaithfulnessProfile, RepresentationSchemeTransition, E.17.ID.CR ComparativeReviewUnit, A.6.4, B.5.2, A.15
• Failed conservativity: name the missing source or condition, repair and recheck a preservation defect within CR when possible, or apply the pattern for the actual changed claim or use. Retargeting uses A.6.4, abductive work uses B.5.2, and action or work claims use the applicable A.15 pattern; explanation, representation change, and other live claims keep their own routes.
• Boundary notes: explanation-facing cases apply ExplanationFaithfulnessProfile; representation-regime shifts apply RepresentationSchemeTransition; bounded comparative review cases apply E.17.ID.CR ComparativeReviewUnit; EntityOfConcern changes apply A.6.4.

A.6.3.CR:End