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 available source claims about the same EntityOfConcern need another textual form, such as a report, summary, translation or filtered restatement. The receiving claims must remain supported by the identified sources under A.6.3.
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. Identify the source claims and resulting text, compare their meaning, and state any omission or loss that affects the intended use. If preservation is doubtful, name the missing basis or defect; repair it within CR when possible, or use the pattern for the changed claim.
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. A same-entity textual rewrite with visible source-relation tether and omission or loss notes, and a repair or next-pattern route when conservativity fails.
Ordinary use. A short source-to-result statement can suffice when the source relation, material omissions and intended use remain recoverable.
Fuller review. Add the information needed when a dispute, risk or intended reliance cannot be settled from that short statement. External citation, cross-context use or a release decision may make preservation, correspondence or use conditions material; they do not by themselves require every field in §4.3.
Use a neighboring pattern when explanation is primary (ExplanationFaithfulnessProfile), the intended operation depends on changing the representation language or reasoning medium (RepresentationTransition), the EntityOfConcern changes (A.6.4), or the work makes a comparative-review claim (E.17.ID.CR). F.9 governs an asserted semantic Bridge or its bounded use; F.9.1 supplies an optional stance note. A coarsened rendering whose loss requires a narrower use and return to the source is governed by A.6.3.CSC Controlled Semantic Coarsening.
A.6.3.CR:2 - Problem
Without a dedicated pattern for conservative textual re-expression:
- report, summary, translation, and filtered rewrite cases are handled ad hoc;
- authors treat textual simplification as if it were automatically conservative;
- the boundary to explanation-facing renderings stays blurry;
- correspondence-mediated rewrites are not distinguished from direct rewrites;
- subsequent users cannot tell whether the result remains a supported restatement or adds interpretation.
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 that affect interpretation or intended use must stay visible.
- Direct vs correspondence-mediated rewrites. Some rewrites use one source episteme; others depend on claims about relations among sources.
- Restatement vs another construction. Explanation, a material representation change and retargeting need their own conditions even when their outputs include text.
- Publication discipline. Admissible MVPK faces and publication renderings matter for textual rewrites.
A.6.3.CR:4 - Solution — entityOfConcernRef-preserving textual re-expression under A.6.3
A.6.3.CR:4.1 - Informal definition
ConservativeRetextualizationspecializes A.6.3 viewing for textual re-expression about the same EntityOfConcern.It preserves the EntityOfConcern resolved by each side’s
entityOfConcernRefunder 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. Its receiving assertions remain subject to A.6.3 conservativity. Separately asserted Bridge, reliance, authorization, Work, evidence or decision claims need their own grounds.
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.b - Local working vocabulary
Use these local terms when distinguishing the source and rendering:
- 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 whose material preservation, correspondence or intended-use question requires more support than the short account supplies.
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 selected U.Episteme is made available, E.24.PUB identifies its audience and bounded-use declarations, the expression and carrier, and the obtaining EpistemePublicationRelation. When a reusable publication form is selected, establish that expression’s conformance to its rules. Form-mediated expression and bearing claims use the same expression as witness. The slice label establishes neither a publication kind nor another episteme identity.
For example, a short restatement shared in a text file can identify the receiving episteme, audience, use, text and file without choosing a reusable form. If the receiving use requires a specified report form, the text must also satisfy that form’s rules. The source tether, omission notes and conservative-rewrite conditions apply in both cases.
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-mediated textual synthesis in which every receiving claim is supported by the named sources and admitted correspondence claims.
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); - a change of representation language or reasoning medium that makes a materially different operation possible, including aligning entries written in the same language for comparison (
RepresentationTransition); - 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 intended operation depends on a change of representation language or reasoning medium, apply RepresentationTransition.
- If the EntityOfConcern changes, apply A.6.4.
A.6.3.CR:4.2.b - What the user checks first
Start with the preservation question:
- Is the published result still about the same EntityOfConcern?
- Does the reader need a clearer restatement, an explanation, or an expression in which a different operation becomes practical? When the last need calls for a change of representation language or reasoning medium, use A.6.3.RT.
- Can the reader see what was omitted, softened, or foregrounded?
- If several sources or correspondence claims contribute, can each receiving claim be traced to those sources and the rule that licenses it?
- 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?
- If any answer is doubtful, is the problem a missing source or condition, a repairable preservation defect, or a 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 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 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 keeps the source claims, preserved meaning and material omissions recoverable. When a changed claim needs another pattern, name that claim and its route. 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.Epistemeclaims are being re-expressed; - that the EntityOfConcern resolved by each side’s
entityOfConcernRefremains 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;
- any changed claim needing another pattern, when that question arises.
Explicit review record (when fuller review is needed). Include or inherit the fields needed to inspect the material preservation, correspondence, source-use or downstream-use question. Assurance, policy and cross-context cases often make such questions consequential. The record may inherit pattern ids and pinned metadata instead of restating them inline. Select only the applicable groups:
- transform relation (
patternSpecializationRef = A.6.3 specialization,relationFunctionClaimRef,sourcePublicationOrRecordForm,targetPublicationOrRecordForm,changeTargetRef); - preservation context (
entityOfConcernPolicy = preserve,boundedContextPolicy,viewpointPolicy,referenceSchemePolicyfor the episteme’s effective interpretation,representationLanguagePolicyfor the language of expression,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).
Use the selected fields to expose the source claims, preserved meaning and conditions on which the receiving use depends.
A.6.3.CR:4.3.a - Ordinary admissibility defaults
Default admissibility for ordinary entityOfConcernRef-preserving textual cases:
- primary admissible faces are
PlainViewandTechCard; - bounded report-only use is admissible when source pins, provenance, loss notes, and entityOfConcernRef-preserving conservativity remain visible;
InteropCarduse is admissible only when the governing publication-face source explicitly permits source-pinned, text-preserving export without added semantics;AssuranceLaneor 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
CorrespondenceModelRefis needed; - the short account identifies the source and any material loss or provenance condition.
CorrespondenceConservativeRetextualization
- the receiving text depends on claims about governed relations among epistemes or views concerning the same EntityOfConcern;
- identify those relations and the supporting claims; when a reference to their describing episteme is needed, local
CorrespondenceModelRefdesignates that episteme under A.6.3:4.5, without introducing a U-kind; - every receiving assertion remains supported by the named sources and admitted correspondence claims, with the same EntityOfConcern and declared material loss.
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.
A.6.3.CR:4.4.a - Recurring same-entity textual moves
Examples of textual moves that can preserve the same EntityOfConcern include:
- 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.
- 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-mediated textual synthesis — one text combines supported claims through identified relations among the sources; any separate Bridge or substitution claim keeps its own conditions.
Each example remains under A.6.3 only while the same-entity and conservativity laws hold.
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 support from the identified available source claims while changing wording, register, language, ordering, or density. Keep conditions on claim scope, publication scope, pins, provenance, grounding and ontic scaffold recoverable where they affect interpretation or intended use. State whether the case is Direct or Correspondence when that distinction is not already obvious.
A.6.3.CR:4.5.b. - Loss and reliability rule
State omissions, foregrounding and source-loss modes that affect interpretation or intended use. A reliability assessment may remain source-bounded or be explicitly downgraded; clearer prose alone does not warrant a higher assessment.
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 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 object or occurrence under its direct obtaining or admission rule, then cite the evidence on which the assertion relies. A 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
For deterministic replay or composition, use A.6.3:4.7. To claim that a further normalization leaves the result unchanged, identify the first and next rewrite arrows, establish the same resulting episteme and the required composite equivalence, and supply a fixture or proof. Different rewrite orders may yield different results. Reopen the affected claims when a needed source, correspondence witness, provenance, publication-form condition or preservation basis is no longer recoverable. Revalidate them when such a dependency changes materially, even if it remains explicit; unaffected claims retain their grounds. E.17:5.1b–c supplies the applicable reopen conditions.
A.6.3.CR:4.5.e. - Correspondence and its receiving use
A correspondence claim used by the rewrite and a claim that the result suits a receiving use are separate. Apply §4.5.c to any Bridge, reliance, authorization or actual-occurrence claim needed by that use; the existence of correspondence alone settles none of them.
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; a 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 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. 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.
For reporting the threshold exceedance, this short slice may inherit the published pins and omit the separate hypotheses because it asserts no cause. A causal decision would need the hypotheses and their qualifications from N-14. The source remains reachable 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 restates the source’s selection rule and preserves its planning and measurement requirements. The summary supports interpretation and source-finding. Keep WP-17 and RM-4 recoverable whenever they affect the stated interpretation, decision or performance; actual use must satisfy the applicable requirements.
A shorter summary used only to select a method family may omit requirements for performing the selected method when that omission does not mislead the reader about the summary’s scope or make M-2 appear ready for execution.
If material loss is admissible only with a narrower use and return to the source, use A.6.3.CSC Controlled Semantic Coarsening with that narrower admissible use, forbidden stronger use, and source-bearing return. For stronger use, apply the 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 summary follows the same source, EntityOfConcern and conservativity conditions as any other rewrite. A model-produced paragraph over an inspection or method-selection note is not an explanation merely because it was generated. Restated claims, material omissions and use conditions must be recoverable. Use the distinctions below when a source-use or support question affects reuse, citation or reliance.
| Source-relation question | CR-local meaning |
|---|---|
| source pointer present | The summary points to the source slice or source bundle it claims to restate. |
| source actually used | The inspectable source relation shows that the generation or rewrite actually used the named source, not merely a similar topic or remembered background. If that historical relation is unavailable, leave it unresolved and block only claims or uses that require it. Retain independently established claim support and uses whose own requirements are satisfied. |
| claim recoverable from source | Each summary assertion can be recovered from the source claims or admitted correspondence witness under the declared rule. |
| claim merely plausible | A sentence sounds likely but is not recoverable from the source. Do not present it as source-backed: retain only a justified source-finding or orientation pointer, or explicitly separate the unsupported proposition and repair it or handle it under the pattern for the new claim. |
| omission or loss | Relevant omitted qualifiers, alternatives, caveats, uncertainty, or conditions are visible enough for the admissible use. |
| claim widening | The summary does not turn possibility, hypothesis, bounded scope, or low-confidence wording into a wider commitment. |
| added linkage | New causal, bridge, comparison, work, gate, evidence, or explanation links are not introduced as if they were in the source. |
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, RepresentationTransition, E.17.ID.CR, A.15, A.10, or another pattern that defines, constrains, or tests the 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 remains in this pattern only while its source relation is explicit and every receiving claim is supported by the design slice, safety slice or admitted correspondence claims. CM-12 names the episteme stating that correspondence; its label alone supplies no witness. Add the review detail needed to establish the claimed overlap.
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.
Russian пока … не uses a negative particle where English until the primary loop fails has none. In both versions the backup continues to watch until the primary has failed two checks in a row. Omitting the second failure or reversing the condition changes the event up to which passive watching is required. The gloss helps an English-only reader follow this difference. 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 is admissible only through narrower admissible use, non-admissible downstream use, and source-bearing return to the 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.
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 transition
A reader can need the same events aligned by component to compare recurrences. The event descriptions can stay in the same language while their arrangement makes that comparison practical. A change of representation language can also make an operation possible. Use RepresentationTransition when that change is the point of the work.
A.6.3.CR:6 - Bias-Annotation
This pattern 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, RepresentationTransition, A.6.4, or the pattern that defines, constrains, or tests the changed claim or use when it requires leaving same-entity textual restatement.
A.6.3.CR:7 - Conformance Checklist
- CC-CR-1 — Same EntityOfConcern remains explicit.
The EntityOfConcern values independently resolved by the source and receiving
entityOfConcernRefvalues are equal. - CC-CR-2 — Textual re-expression remains the right family. The intended use is served by a textual restatement. Check whether the reader instead needs an explanation or an operation made possible by a change of representation language or reasoning medium.
- CC-CR-3 — Material loss, provenance, pinning, and reliability conditions remain recoverable. The case makes conditions that affect interpretation or intended use recoverable from the text, its surrounding publication, or the source references on which that use depends.
- CC-CR-4 — Direct or correspondence-mediated construction is identifiable. The source relations make the profile recoverable; state and justify the distinction explicitly when it is not obvious.
- CC-CR-5 — Correspondence witness is named where needed.
If correspondence-mediated, identify the relations and supporting claims; use
CorrespondenceModelRefwhen their describing episteme must be cited. - 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.
- 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 changed claim. Repair and recheck within CR when the intended restatement can be restored. For a different claim or use, name the pattern to use next (
ExplanationFaithfulnessProfile,RepresentationTransition,A.6.4,B.5.2, or another applicable pattern). - 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
| Anti-pattern | Why it is wrong | How to avoid it |
|---|---|---|
| Treating every summary as automatically conservative | summary demand hides omission and claim shift | compare receiving claims with the sources and the declared rule; expose material loss and provenance conditions |
| Hiding correspondence in plain paraphrase | the relations and claims needed to support the rewrite disappear into prose | identify those relations and claims, and cite their describing episteme when needed |
| Letting a rewrite become explanation | explanation work quietly becomes a textual “rewrite” | apply explanation governance once didactic or explanatory work dominates |
| Letting the EntityOfConcern shift by topic similarity | same topic is not the same EntityOfConcern | independently resolve the source and receiving entityOfConcernRef values; apply A.6.4 if the resolved entities differ |
A.6.3.CR:9 - Consequences
- Readers can inspect the connection between the source claims and the rewritten text.
- Direct and correspondence-mediated variants stay visibly separated.
- Loss, provenance, and reliability conditions that affect interpretation or intended use remain recoverable.
- 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
Conservativity depends on what the text commits the reader to, not on shared vocabulary alone. Recovering the source claim and its modality, conditions and alternatives makes a changed commitment visible. That comparison guides a local repair: restore a lost condition, declare an admissible omission, or separate a new claim for its own justification. Direct and correspondence-mediated cases use the same test, with the latter also depending on the identified relations among sources.
A.6.3.CR:11 - Source contributions and limits
The source lines below inform different parts of textual preservation. The same-EntityOfConcern and episteme-identity rules are FPF conditions; they are not supplied by a citation alone.
| Question | Source contribution | Source | FPF use and boundary |
|---|---|---|---|
| Which description relations must remain distinguishable? | Architecture-description practice distinguishes views, viewpoints and correspondence. | ISO/IEC/IEEE 42010:2022 | A.6.3 and E.17.0 separately govern FPF construction and view membership; C.2.1 supplies the EntityOfConcern identity condition. |
| Does a summary remain supported by its source? | Summarization factuality work examines unsupported content and source faithfulness. | Maynez et al. (2020), On Faithfulness and Factuality in Abstractive Summarization | Source-sensitive checking is used here to inspect omissions, strengthening and added links. Passing a source-support test still does not establish suitability for a receiving use. |
| Does translation preserve the intended claims? | MQM distinguishes accuracy issues, including omission and addition, from fluent expression. | W3C Multidimensional Quality Metrics Community Group and MQM issue-type framework | These distinctions help inspect translation; the FPF same-entity, provenance and use conditions remain separate. |
| Does simpler prose preserve commitments? | Plain-language practice organizes communication around its intended reader and use. | ISO 24495-1:2023 | Reader-oriented rewriting remains subject to the source conditions and conservativity test in §4.5.f; readability alone does not establish preservation. |
For source recoverability, independent-verification claims and reopening, use the distinction needed from E.17:5.1b. E.17:5.1c supplies shared use-boundary terms and E.17:5.1d selects the primary boundary. Those rules apply here to same-entity textual restatement.
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,RepresentationTransition,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 changed claim or use. Retargeting uses
A.6.4, abductive work usesB.5.2, and action or work claims use the applicableA.15pattern; explanation, representation change, and other live claims keep their own routes. - Boundary notes: explanation-facing cases apply
ExplanationFaithfulnessProfile; changes of representation language or reasoning medium material to the operation applyRepresentationTransition; bounded comparative review cases applyE.17.ID.CR ComparativeReviewUnit; EntityOfConcern changes applyA.6.4.