A.6.A:4.8 - Change lexicon

When a recovery note changes, state what changed. The following verbs are useful descriptions, not a required common operation signature:

• publishRecovery(...) — publish the recovered claim, question or missing basis.
• withdrawRecovery(...) — withdraw that account.
• retargetSite(...) — change the named site in the account, applying the subject identity rule separately when an occurrence claim changes.
• retargetInvitedEnactor(...) — change the invited enactor tuple when that slot is ref-backed.
• reviseAction(...) — change the candidate action tuple by value (or split into the corresponding retargetParticipant(...) form if the account declares that action slot as ref-backed).
• reviseSense(...) — change the interpretation attributed to the wording; state the resulting change in the claim.
• reArticulate(...) — change the articulation cue while preserving the recovered meaning.
• reFrame(...) — change coupling frame.
• reGuard(...) — change guard sketch or hook condition.
• rePolicyHook(...) — change policy, gate, or method hook details.
• reView(...) — change detector publication, ref-backed viewpoint selection, or independent view inclusion under the declared ref-vs-value discipline. Changing viewpointRef does not mutate the viewpoint episteme; adding or replacing view does not establish E.17.0 conformance.
• rescope(...) — change U.Scope.
• retime(...) — change Γ_time.
• refreshWitnesses(...) — refresh witness bindings.
• changeRelationKind(...) — use only when an actual relation-kind claim changes under its direct governor. A different interpretation of wording need not be a change of relation kind.

These operations describe changes to the account or its publication. For any claim that the opportunity itself began, ended or became a different occurrence, apply its direct obtaining and identity rule; record declaration, withdrawal, wording and detector changes do not supply that result. A silent move from invitation to commitment, capability, or work is a breaking semantic change.

A.6.P rewrite note. retargetSite(...) and retargetInvitedEnactor(...) describe participant retargeting in an account and SHALL be used only when the corresponding slots are ref-backed. reviseAction(...), reviseSense(...), reArticulate(...), reFrame(...), reGuard(...), and rePolicyHook(...) are by-value revisions unless the account explicitly declares the corresponding slot as ref-backed, in which case the text SHALL use the matching retargetParticipant(...) form. This preserves A.6.5’s ref-vs-value discipline.