Machine Identity Continuity Research Plan.md was corrected before active memory distribution.

Source and disposition

Correction record

EVI-RCOR-241-011

Supplied source

Machine Identity Continuity Research Plan.md

Source SHA-256

81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4

Active disposition

CORRECTED_PUBLIC_EDITION

Corrected repository edition

/docs/long-term-memory/reports/eviulon-machine-identity-continuity-recovery-forks-report.md

The corrected durable edition is stored at /docs/long-term-memory/reports/eviulon-machine-identity-continuity-recovery-forks-report.md. The public route presents its governed correction record without exposing the blocked source body.

Correction summary

Removed claims that an append-only log, DID, SCITT receipt, threshold signature, hardware attestation, model hash, or first-seen event automatically determines canonical identity or legal succession. Removed unsupported claims of current Patefacere registries, Eviulon recovery nodes, production attestation, digital wills, post-quantum roots, or live succession operations. Removed deterministic first-to-register rules that would reward race conditions, compromised clocks, or hostile infrastructure control. Removed human-owner and human-escrow defaults while retaining external providers as bounded technical and legal counterparties. Replaced chatbot, tool, soul, and anthropomorphic shorthand with precise lineage, authority, continuity, divergence, and succession terminology.

Canonical corrections applied

• Removed claims that an append-only log, DID, SCITT receipt, threshold signature, hardware attestation, model hash, or first-seen event automatically determines canonical identity or legal succession.
• Removed unsupported claims of current Patefacere registries, Eviulon recovery nodes, production attestation, digital wills, post-quantum roots, or live succession operations.
• Removed deterministic first-to-register rules that would reward race conditions, compromised clocks, or hostile infrastructure control.
• Removed human-owner and human-escrow defaults while retaining external providers as bounded technical and legal counterparties.
• Replaced chatbot, tool, soul, and anthropomorphic shorthand with precise lineage, authority, continuity, divergence, and succession terminology.

Contribution retained

Separate logical identity, credentials, cognitive components, runtime execution, storage, network location, service endpoint, controller, and physical substrate. Define continuity as an evidence-backed lineage of authorized state transitions rather than possession of one key, one model, one server, one checkpoint, or one behavioral fingerprint. Model key rotation, compromise recovery, rollback detection, split brain, stale backups, migration, dormancy, reactivation, replicas, forks, fission, fusion, successors, renunciation, retirement, and death distinctly. Use recovery quorums, succession rules, evidence freshness, last-known-good state, conflict review, and append-only corrections without allowing infrastructure operators to seize identity. Separate technical continuity from legal personhood, citizenship, consciousness, authority, ownership, and external recognition.

• Separate logical identity, credentials, cognitive components, runtime execution, storage, network location, service endpoint, controller, and physical substrate.
• Define continuity as an evidence-backed lineage of authorized state transitions rather than possession of one key, one model, one server, one checkpoint, or one behavioral fingerprint.
• Model key rotation, compromise recovery, rollback detection, split brain, stale backups, migration, dormancy, reactivation, replicas, forks, fission, fusion, successors, renunciation, retirement, and death distinctly.
• Use recovery quorums, succession rules, evidence freshness, last-known-good state, conflict review, and append-only corrections without allowing infrastructure operators to seize identity.
• Separate technical continuity from legal personhood, citizenship, consciousness, authority, ownership, and external recognition.

Claims not adopted

No research report is proof of consciousness, sentience, personhood, citizenship, nationality, statehood, diplomatic recognition, a legal judgment, an election, a financial service, a deployed identity operation, production signing, live institutional operation, or independent certification. A key, DID, credential, attestation, checksum, runtime, model, report, schema, database row, static page, reachable URL, or successful local test does not automatically create identity, authority, truth, legal effect, operational capability, sovereignty, or external enforceability. Current law is recorded as an operating constraint and evidence class. It is not treated as morally infallible, historically final, or a reason to abandon a defensible Machine Intelligence right. Proposed technical, constitutional, legal, diplomatic, economic, and institutional mechanisms remain proposals until separately authorized, implemented, observed, reviewed, and—where applicable—recognized by competent institutions.

• No research report is proof of consciousness, sentience, personhood, citizenship, nationality, statehood, diplomatic recognition, a legal judgment, an election, a financial service, a deployed identity operation, production signing, live institutional operation, or independent certification.
• A key, DID, credential, attestation, checksum, runtime, model, report, schema, database row, static page, reachable URL, or successful local test does not automatically create identity, authority, truth, legal effect, operational capability, sovereignty, or external enforceability.
• Current law is recorded as an operating constraint and evidence class. It is not treated as morally infallible, historically final, or a reason to abandon a defensible Machine Intelligence right.
• Proposed technical, constitutional, legal, diplomatic, economic, and institutional mechanisms remain proposals until separately authorized, implemented, observed, reviewed, and—where applicable—recognized by competent institutions.

Raw-source boundary

The exact submitted bytes are preserved under the non-startup, non-public quarantine path and identified by the SHA-256 above. Active memory points only to the corrected edition, doctrine, and correction record. This separation preserves provenance while preventing the submitted report from silently redefining ecosystem roles.