A.6.6:4.6 - Base-change operation lexicon

The following local labels classify changes to an optional assertion episteme or reusable declaration when a named receiver needs that history. They do not describe the beginning, ending, or change of the world-side relation itself, and an ordinary direct assertion needs none of them. In decision or publication use, preserve the prior episteme when changing its ClaimGraph, exact EntityOfConcern, or effective ReferenceScheme; such a change identifies another episteme. A representation-only edit need not do so. Claim edition continuity only when the C.2.1:4.5 rule and case facts establish it.

Operation classes (conceptual):

1. declareBase - create a new optional assertion with explicit dependent, base, directRelationKind, and assertionPolarity, or a new reusable declaration for that same already governed direct relation kind; add only the scope, time, evidence-use, or other qualifications that its direct predicate or named receiver needs.
2. withdrawBaseDecl — retire an assertion or declaration (or render it inapplicable by scope narrowing or time restriction, depending on the direct relation’s declaration).
3. rebase — change base while keeping the same dependent and directRelationKind (legality depends on the direct relation’s declaration; often requires witness refresh).
4. repointDependent — change dependent while keeping the same base and directRelationKind.
5. rescope — change scope (widen/narrow/translate) under the direct relation’s scope rule; widening often triggers witness refresh.
6. retime — change Γ_time selector/policy when time matters; not a substitute for witness-timespan/freshness predicates.
7. refreshWitnesses — add/refresh witnesses/pins when decision use continues across time advances, scope widening, or evidence refresh.
8. changeDirectRelationKind — not an edit-in-place. Changing directRelationKind changes claim meaning; mint a new assertion or declaration rather than silently rewriting the kind. When edition history is needed, relate it to the prior episteme only if C.2.1:4.5’s continuity rule and case facts establish that relation. Use F.13 for a separately current lexical-continuity claim.

Relation to A.6.5 slot operations (non-normative mapping). A project may realize an edit to an optional assertion or declaration through A.6.5 slot operations. The semantic account must still say which episteme field changed. A separately claimed change to the actual relation uses the direct relation’s change rule and any current Work; it is never inferred from the record edit.

Relation to E.18 assurance ops (informative). On U.Transfer, ConstrainTo, CalibrateTo, CiteEvidence, and AttributeTo have their own declared meanings and constraints. A project may use the local declaration-change labels to describe changes in a represented assertion, but those labels neither subsume the E.18 operations nor create their relations.