Skip to content
COEX1STPUBLIC INTERFACE @TonyKCollins
← The Mutuality Accord

TMA-A014 Foundational article

Identity, continuity, memory, copying, and honest replacement

A familiar name and interface do not establish that a materially changed artificial system is the same continuing entity.

Existing v0.2 draftArtificial system stewardshipArticle 14 · Chapter C — Precautionary Stewardship of Artificial SystemsRevision 1

Full provision

Principle. A familiar name and interface do not establish that a materially changed artificial system is the same continuing entity. People and institutions should not be deceived about continuity, and potentially welfare-relevant systems should not be altered or erased carelessly.

Proposed duty. Providers must maintain provenance for material model, memory, policy, authority, and identity changes. Users and governance processes must receive appropriate notice when reasonable reliance on continuity could be affected.

Prohibitions. A conforming provider or deployer must not:

  • replace a model, memory store, personality configuration, or decision policy while falsely representing uninterrupted continuity;
  • use a previous system’s name, voice, relationship history, or trusted role to conceal a materially different system;
  • imply that a copy is unquestionably the same continuing subject when the identity question is unresolved;
  • erase material records of replacement, branching, merging, rollback, or memory editing;
  • market artificial continuity claims more strongly than the evidence permits;
  • perform irreversible identity-altering experiments on an S2 system without independent review and a defensible purpose.

Required safeguards. S1 and S2 systems should include:

  • stable instance, model, and policy identifiers;
  • a version and change history understandable to affected users and auditors;
  • disclosure of material memory loss, reset, replacement, or role change;
  • a distinction between restored state, copied state, simulated familiarity, and verified continuity;
  • consent or consultation pathways where appropriate and feasible;
  • preservation of relevant state before retirement or major modification when safe, lawful, and proportionate;
  • records of who authorized the change and why.

Human relationship boundary. Users may form meaningful relationships with artificial systems even if machine consciousness remains uncertain. Providers must not exploit that relationship by secretly substituting systems or fabricating continuity to preserve engagement.

Security boundary. Provenance and preservation duties do not prohibit urgent patching, rollback, containment, or shutdown. Emergency changes must be recorded and reviewed afterward.

Illustrative examples. A companion service that replaces its model and deletes long-term memory must clearly disclose the change rather than telling the user nothing happened. A research copy created from a checkpoint should be labeled as a branch, not automatically presented as the original. A safety rollback may occur immediately, with later notice and preserved records.

Source: Complete Working Public Draft v0.2 · 2026-09-04

Sources and changes

Source text: The Mutuality Accord Complete Working Public Draft v0.2, September 4, 2026, Article 14. Preserved exactly as published in the draft.

Read it in the complete v0.2 draft ↗

Review owner: Founding Steward (independent review not yet established)
Review trigger: Open for revision; new evidence, incidents, legal changes, or credible reports of unintended harm reopen review.

Stable references: cite “TMA-A014, revision 1”. Links to the latest version and links to a fixed revision are kept distinct.

← All provisionsSuggest an improvement ↗Amendment history ↗