A.6.S:4.3 - Change discipline: Viewing vs Retargeting vs editing

When more than one distinction is current, classify each move separately rather than forcing all four buckets into every revision:

1. Publication form and conditional viewing. A presentation change (views, stakeholder cards, projections) may be an E.17/E.24.PUB form or carrier change. Use A.6.3 only when a mathematical source-to-receiving viewing construction is current, preserving the exact EntityOfConcern; E.17.0 separately governs any U.View membership claim.

2. Direct edits and conditional declaration history. State a one-off vocabulary, law, applicability, or reference change directly. Use A.6.5 only for reusable relation-participant declarations or reference operations that matter to the receiver. Use A.6.6 declaration history only after the actual base-dependence relation is stated and a named receiver needs that history.

3. Editioning + reference retargeting (A.6.5). Use when the TargetSignature meaningfully changes and downstream coordination needs a new TargetSignature edition. Do not silently mutate the existing episteme: identify the successor edition and retarget the references whose receiving use now selects it (Retarget<...> in the relevant Ref slots).

4. Epistemic retargeting and structural reinterpretation (A.6.4; rarer). Use only when the source and receiving EntityOfConcernRef values resolve to different exact EntitiesOfConcern. A reference-only change that still resolves to the same entity stays with its actual reference operation. A.6.4 identifies the source and receiving epistemes and one exact arrow r. A separate C.2.1 bounded-use assertion q is about that exact r; its ClaimGraph contains the invariant, visible loss, named receiving use, conditions, and affirmative or negative polarity. A separate current-case judgement compares the exact facts with q and returns exactly satisfies, fails, or cannot decide; cannot decide names the missing fact and reopen condition. This is distinct from an ordinary new edition of the same TargetSignature.

Rule of thumb:

• If only the publication form or carrier changes, use E.17/E.24.PUB and stop; no slot/base declaration is required unless another receiving use needs it.
• If the change is “new TargetSignature edition for consumers”, identify the new edition and explicitly retarget the references whose receiving use now selects it.
• If the change is a different EntityOfConcern, use A.6.4’s three-part account: the exact arrow r, a separate C.2.1 bounded-use assertion q, and a separate current-case judgement. A kind difference alone identifies none of them.

EFEM discipline. When a constructor operation really uses an A.6.2 arrow family, declare its endpoint comparison and entityOfConcernChangeMode under A.6.2. An operation description that needs no mathematical arrow introduces none. Editioning is orthogonal: you MAY mint a new edition even under preserve; references whose receiving use now selects that edition MUST be retargeted explicitly, with A.6.5 slot discipline where applicable. For an actual measurement, actuation, validation run, carrier write, or other effect, identify any claimed operation application under A.6.1, changed-object or effect claim under its direct rule, and Work under §4.0 independently. An effect alone establishes neither application nor Work; the A.6.2 arrow performs none of these actions.