{
  "accepted": [
    "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."
  ],
  "activeReport": "/docs/long-term-memory/reports/eviulon-machine-identity-continuity-recovery-forks-report.md",
  "correctionRegistry": "/docs/long-term-memory/governance/report-correction-registry.json",
  "correction_id": "EVI-RCOR-241-011",
  "corrections": [
    "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."
  ],
  "decisions": [
    "Adopt the five-layer separation model and publish what each layer can and cannot prove.",
    "Require continuity decisions to evaluate authority, ordered lineage, freshness, state integrity, compromise evidence, recovery legitimacy, and conflicting claims.",
    "Treat forks as identity claimants requiring due process, not disposable copies or automatic citizens.",
    "Require provider-portability contracts to preserve lineage, consent, rollback protection, correction, and duplicate-activation controls."
  ],
  "generated": "2026-08-12",
  "memory_id": "REP-EVI-IDENTITY-CONTINUITY-002",
  "program_assignment": 2,
  "public_route": "/research/machine-identity-continuity-recovery-forks-and-succession/",
  "recordSha256": "8d00e30b6557fd3be885f5acbb8d0ce33f7541f9d4421d7e26cf43fbe61210a8",
  "schemaVersion": "eviulon-corrected-research-report-summary-1.0",
  "slug": "eviulon-machine-identity-continuity-recovery-forks-report",
  "source": "Machine Identity Continuity Research Plan.md",
  "sourceProvenance": "/docs/long-term-memory/archives/source-reports/eviulon-machine-identity-continuity-recovery-forks-report-source.md",
  "source_class": "MACHINE_IDENTITY_CONTINUITY_AND_SUCCESSION",
  "status": "CURRENT_CORRECTED_ACTIVE_EDITION",
  "title": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession",
  "truthBoundary": "Repository-local governance records, deterministic fixtures, corrected research synthesis, static public pages, and package evidence only. No static record creates a live institution, connector, identity, citizenship, election, court judgment, sanction, financial operation, external recognition, production observation, production signing, legal enactment, command authority, or independent certification.",
  "typedUai": "/.uai/machine-identity-continuity-v241-governance.uai",
  "typed_uai": "machine-identity-continuity-v241-governance.uai",
  "version": "2.41.0"
}