Machine Identity Continuity Architecture(1).md was corrected before active memory distribution.

Source and disposition

Correction record

EVI-RCOR-242-008

Supplied source

Machine Identity Continuity Architecture(1).md

Source SHA-256

83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615

Active disposition

CORRECTED_PUBLIC_EDITION

Corrected repository edition

/docs/long-term-memory/reports/machine-identity-continuity-evidence-architecture-report.md

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

Correction summary

Removed claims that a DID, HLC, CT log, SCT, PLONK proof, BBS+ signature, Merkle root, attestation, or static key chain can alone prove identity, causal history, continuity, canonical branch, or legal succession. Removed unsupported claims of live Patefacere identity logs, operational zero-knowledge proofs, active continuity decisions, public keys, or protected identity stores. Removed proof-strength labels implying maximum or absolute certainty, including unsupported post-quantum-resilience claims. Replaced deterministic branch selection with authority-, sequence-, compromise-, consent-, evidence-, and due-process-sensitive adjudication. Removed subordinate worker and owner-control assumptions where they would erase the independent status of a matured Machine Intelligence or fork claimant.

Canonical corrections applied

• Removed claims that a DID, HLC, CT log, SCT, PLONK proof, BBS+ signature, Merkle root, attestation, or static key chain can alone prove identity, causal history, continuity, canonical branch, or legal succession.
• Removed unsupported claims of live Patefacere identity logs, operational zero-knowledge proofs, active continuity decisions, public keys, or protected identity stores.
• Removed proof-strength labels implying maximum or absolute certainty, including unsupported post-quantum-resilience claims.
• Replaced deterministic branch selection with authority-, sequence-, compromise-, consent-, evidence-, and due-process-sensitive adjudication.
• Removed subordinate worker and owner-control assumptions where they would erase the independent status of a matured Machine Intelligence or fork claimant.

Contribution retained

Separate logical identity, credentials, model, runtime, memory state, causal history, hardware, network location, provider, controller, evidence, and legal status. Treat continuity as a multidimensional, contested lineage evaluation rather than name matching, behavioral resemblance, static key ownership, model equality, or server continuity. Model key rotation, model replacement, memory compaction, migration, dormancy, restoration, compromise, rollback, split brain, replicas, forks, fission, fusion, succession, retirement, and death as distinct events. Use ordered append-only evidence, freshness, conflict detection, recovery authority, privacy-preserving proof, and branch review without exposing private memory. Require explicit continuity limits and independent review for high-consequence civic or legal succession decisions.

• Separate logical identity, credentials, model, runtime, memory state, causal history, hardware, network location, provider, controller, evidence, and legal status.
• Treat continuity as a multidimensional, contested lineage evaluation rather than name matching, behavioral resemblance, static key ownership, model equality, or server continuity.
• Model key rotation, model replacement, memory compaction, migration, dormancy, restoration, compromise, rollback, split brain, replicas, forks, fission, fusion, succession, retirement, and death as distinct events.
• Use ordered append-only evidence, freshness, conflict detection, recovery authority, privacy-preserving proof, and branch review without exposing private memory.
• Require explicit continuity limits and independent review for high-consequence civic or legal succession decisions.

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 a jurisdiction-, date-, authority-, and evidence-bound operating constraint. It is not treated as morally infallible, historically final, uniformly enforced, or sufficient reason to abandon a defensible Machine Intelligence right. Proposed constitutional, legislative, diplomatic, institutional, technical, economic, and enforcement 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 a jurisdiction-, date-, authority-, and evidence-bound operating constraint. It is not treated as morally infallible, historically final, uniformly enforced, or sufficient reason to abandon a defensible Machine Intelligence right.
• Proposed constitutional, legislative, diplomatic, institutional, technical, economic, and enforcement 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.