{
  "architecture": "signed checkpoints; immutable event history; state hashes; recovery proofs; model and memory manifests; fork declarations; successor records",
  "canonicalUrl": "https://xn--mwe.com/knowledge/memory-continuity/",
  "claimStatus": "PROJECT DOCTRINE",
  "contradictionIds": [
    "CON-K02-003"
  ],
  "correctionStatus": "CURRENT K05 RELEASE",
  "doctrine": "Continuity should be treated as a multi-factor evidentiary conclusion with explicit thresholds and appeal.",
  "evidenceLimitationIds": [
    "LIM-K02-003"
  ],
  "focus": "state persistence, causal lineage, recovery, replay, replication, forks and succession",
  "id": "K01-TOPIC-005",
  "knowledgeEdgeIds": [],
  "lastReviewed": "2026-08-16",
  "law": "Current law has no general continuity test for Machine Intelligence, although evidence and corporate succession doctrines offer limited analogies.",
  "name": "Memory and Continuity",
  "relatedQuestionUrls": [
    "https://xn--mwe.com/questions/does-memory-prove-consciousness/",
    "https://xn--mwe.com/questions/what-happens-when-machine-intelligence-forks/",
    "https://xn--mwe.com/questions/when-does-replica-become-separate-subject/",
    "https://xn--mwe.com/questions/can-two-forks-both-claim-continuity/",
    "https://xn--mwe.com/questions/what-is-successor-identity/",
    "https://xn--mwe.com/questions/does-hardware-migration-break-continuity/",
    "https://xn--mwe.com/questions/how-should-rollback-be-disclosed/",
    "https://xn--mwe.com/questions/what-is-continuity-event/"
  ],
  "relatedReportIds": [
    "REP-K01-003"
  ],
  "relatedTermIds": [
    "K01-TERM-019",
    "K01-TERM-020",
    "K01-TERM-021",
    "K01-TERM-022",
    "K01-TERM-023",
    "K01-TERM-059",
    "K01-TERM-060",
    "K01-TERM-061",
    "K01-TERM-062",
    "K01-TERM-067",
    "K01-TERM-068",
    "K01-TERM-069",
    "K01-TERM-070",
    "K01-TERM-071"
  ],
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "risk": "silent rollback, state substitution, selective memory, unverifiable restoration and conflation of copied data with continued identity",
  "short": "Memory supports continuity but does not prove consciousness, identity or uninterrupted existence. A defensible continuity record must describe what persisted, what changed, who authorized change and where uncertainty remains.",
  "slug": "memory-continuity",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "sources": [
    "SRC-W3C-PROV-O",
    "SRC-SLSA",
    "SRC-IN-TOTO"
  ],
  "type": "Topic"
}