A.6.3.CSC:5.1 - Worked slices

Direct text shortening (ordinary form). The source paragraph says: Release only after a current smoke-test pass; rollback must remain available; a designated approver must approve any exception. The deployment guide then gives six implementation details not needed by the current planner. The practitioner marks the three decision conditions as must-retain and writes: Release only after a current smoke-test pass; keep rollback available; every exception needs approval by a designated approver. Comparison records the omitted implementation details, confirms that the candidate adds or strengthens no unsupported claim, blocks audit/evidence/release-authority use from the candidate alone, and points back to the paragraph on dispute or independent reuse. A variant that keeps all three conditions but adds therefore release is approved is rejected at the same comparison: the source states preconditions and an exception rule, not current approval status. The faithful candidate remains with its linked source, and the invented-status variant is discarded; the local comparison needs no separate card or C.2.1 dossier. If the faithful candidate will be cited in a release decision, the exact branch identifies X, Y, and c and adds only the source, work, evidence, gate, or assurance relations that decision needs.

Manager orientation summary. Exact source episteme IR-42-X states trace, confidence-band, alternative-branch, and incident claims about exact incident IR-42 under its effective incident-analysis scheme. Exact coarsened episteme IR-42-Manager-Y states the narrower cache-failover orientation claim about the same incident under its effective briefing scheme. ManagerCoarsening : X -> Y preserves the leading-concern claim, drops confidence bands and alternatives, blocks approval/audit/release/causal/work-order use, and returns to X. A dashboard tile and its carrier merely expose Y.

Redacted partner note. Exact source episteme IncidentDisclosure-X and exact receiving episteme PartnerDisclosure-Y concern the same incident. Their declared coarsening omits actor identity and trace path for bounded disclosure, preserves coordination claims, blocks accountability/legal/audit/readiness/gate use, and returns to X or the exact authority destination. The note form, redaction layout, and carrier are not either episteme.

Redacted functional-description publication. Exact source episteme FunctionalArchitecture-X states flow relations, method-selection limits, work-plan prerequisites, result-measurement requirements, and two exception claims about one exact system. Exact partner episteme FunctionalPartner-Y concerns the same system; PartnerFunctionalCoarsening : X -> Y preserves the main flow claim, removes exceptions and measurement detail, permits bounded coordination orientation, blocks work/gate/evidence/justification/control/release use, and returns to X. A partner table and carrier expose Y through E.24.PUB.

Coarsened narrative briefing. Exact source episteme ArchitectureCandidates-X states three candidate, two trade-off, and one unresolved-constraint claims about one exact system. Exact briefing episteme CandidateBriefing-Y concerns the same system. NAR supplies the narrative-ordering account; CSC supplies the declared omission of alternatives, orientation-only use, blocked selection/decision/implementation/evidence use, and return to X. The briefing form is neither endpoint.

Exceptional interop-facing simplification. Exact source episteme ExchangeComparison-X states the bounded source-local claims and exact comparison or Bridge dependencies. Exact orientation episteme ExchangeGloss-Y states the narrower broader-than gloss about the same comparison EntityOfConcern. InteropCoarsening : X -> Y does not establish equivalence, projection, substitution, or a Bridge; establish the operative relation and support its bounded use under its governing pattern, or return to X. When the claim needs a Bridge between exact local senses with different interpretation bases, use F.9 and a separate bounded-use claim. An F.9.1 stance note may explain that claim but cannot replace it.

Bad fit: hidden work authority. Deployment may proceed; see summary S-3. The sentence claims permission to deploy on the basis of a summary. Select the matching A.6 A6-AW-* row for that permission assertion and follow its direct subject pattern; use the applicable A.15 pattern if a Work plan or actual Work is also claimed. Reopen the source-bearing side before any work or approval claim proceeds.