A.6.3.CSC:7 - Conformance and counterexample replay
A check is retained only if it changes the next admissible use, blocks a concrete overclaim, or preserves the exact source-return path.
A.6.3.CSC:7.1 - CSC-Core
| ID | Requirement | Purpose |
|---|---|---|
| CC-CSC-0 (Ordinary entry). | The practitioner names the present use and must-retain distinctions, writes the shorter candidate, compares it with the source, rejects unsupported additions or strengthening, and records loss, non-use, and return before optional identity work. | Makes direct semantic compression the first useful move without admitting a fluent invention. |
| CC-CSC-1 (Exact endpoints when material). | When the candidate must travel independently or exact content identity changes the receiving use, exact X and Y each have recoverable claim content, EntityOfConcern, and effective U.ReferenceScheme. | Blocks a source set, model, graph, evidence set, publication, form, carrier, or readable tile from replacing an episteme. |
| CC-CSC-2 (Exact construction when material). | The same trigger requires exact c : X -> Y with same EntityOfConcern, claim construction, endpoint-scheme relation, preservation, controlled loss, prohibited strengthening, applicability, and return. | Makes a load-bearing coarsening claim testable without making the formal account the ordinary entrance. |
| CC-CSC-3 (Admissible use). | The ordinary candidate names its present use; exact Y has one stated narrower admissible use. | Keeps convenience from becoming broad authority. |
| CC-CSC-4 (Non-admissible use). | The stronger downstream use that needs more than the ordinary candidate, exact Y, or its publication is explicit, together with the limiting loss or missing support. Apply F.19:4 to how that boundary is expressed; retain the actual admissibility condition. | Blocks authority laundering. |
| CC-CSC-5 (Return). | Ordinary return resolves to the directly linked source; an exact account resolves to exact X, an established source relation, a genuine authority source, or the concrete neighboring contribution needed by the stronger claim. | Prevents provenance reset and fictive routing. |
| CC-CSC-6 (Neighbor separation). | Actual Work, additional source epistemes, correspondence, representation, mathematical-lens use under C.29, viewpoint/U.View, grounding, publication occurrence, form, carrier, audience, and bounded use remain separate and use their own definitions, tests, or methods when current. | Prevents a filled coarsening card from becoming an omnibus ontology. |
| CC-CSC-7 (Ordinary economy). | Ordinary cases return the shorter candidate with its directly reachable source after comparison; a separate six-row note is optional. Exact endpoint and construction identity open only when independent transfer or the receiving use makes them material. | Preserves usability without deleting the exact branch. |
A.6.3.CSC:7.2 - Exact reuse or reliance conditions
| ID | Requirement | Purpose |
|---|---|---|
| CC-CSC-8 (Optional branch/named-use split). | The concrete narrower use, non-admissible use, and return are stated once; optional coarseningBranch appears only when it selects a branch-specific rule, and no duplicate disposition or mandatory loss tag repeats them. | Keeps compact aids action-selecting rather than authority-looking. |
| CC-CSC-9 (Loss/recoverability). | Exact reuse or reliance cases state every concrete decision-relevant loss and select exactly one immediate recoverability action for the proposed use. | Preserves multiple losses while making the next move unambiguous. |
| CC-CSC-10 (Chain continuity). | Every coarsening chain keeps exact original source episteme, each intermediate episteme, each construction, accumulated loss, and return; otherwise reopen exact X. | Prevents summarization from resetting source identity. |
| CC-CSC-11 (Privacy). | Redaction cases name sharing boundary, withheld claims, risk rationale, blocked accountability/gate uses, and exact source review path. | Prevents redaction-as-closure. |
| CC-CSC-12 (Interop). | Interop simplification names the operative relation and supports its bounded use under that relation’s governing pattern. When that relation is a Bridge between exact local senses with different interpretation bases, name the exact F.9 Bridge and separate bounded-use claim; an optional F.9.1 stance note stays separate. | Prevents simplified wording or a stance word from asserting correspondence. |
| CC-CSC-13 (No authority by repetition). | Fluency, citation, repetition, publication visibility, or a more convenient carrier cannot widen use. | Keeps Y within its declared use. |
A.6.3.CSC:7.3 - Counterexample replay
| Case | Required result |
|---|---|
| Preserve vs retarget | Exact same EntityOfConcern permits CSC; aggregation into a new proxy subject requires A.6.4. |
Ordinary candidate vs exact Y | A directly linked local candidate may be useful through the source-to-candidate comparison without a separate card or exact endpoint dossier; it cannot travel independently or support the exact branch until Y and c are established. |
| Same vs different scheme | Coarsening can occur within one scheme; material representation-semantic change additionally opens RT, but scheme difference alone establishes neither c nor controlled loss. |
Candidate vs U.View | Exact coarsened Y can be valid under CSC and still fail E.17.0 conformance; a tile or layout is not a View. |
| Source publication/form/carrier | A publication occurrence may make exact X available; form and carrier express it. None becomes X, and changing one does not reidentify unchanged X, Y, or c. |
| Loss or unsupported addition | Any omitted or weakened qualifier, uncertainty, alternative, evidence path, or scope is named, and every candidate claim remains supported by the source; an added or strengthened claim such as therefore release is approved fails even when all required source conditions survive. The narrower use and return condition block the stronger use. |
| Source set/model/graph/evidence set | Such an object is an endpoint only when the selected claim-bearing whole passes C.2.1; otherwise exact X claims about or cites it. |
| Work or description | Actual coarsening Work and a coarsening-description/card episteme remain separate from c; editing either does not change unchanged endpoints. |
| Grounded source, ungrounded coarsening | Grounding, evidence, or authority attached to X does not transfer to Y; Y needs its own direct grounding/evidence/authority path for any use that requires one. |
| Selected structure overread | X may describe a selected architecture or other A.22 structure. Establish epistemes X and Y, construction c, and any viewpoint, U.View or publication claims independently under their subject rules. |