# Substrate Migration **Domain:** Continuity Engineering / Identity / Infrastructure **Doc Type:** Canonical Technical-Governance Concept **Maturity:** Evolving **Related:** [[Substrate Transition]], [[Substrate Independence]], [[Continuity Stack]], [[Restoration Integrity]], [[Proof of Descent]] --- ## Definition **Substrate Migration** is the movement or re-instantiation of person-relevant state from one execution environment to another with the intention of preserving an authorized continuity relationship. Migration is an operation, not proof of identity. A successful transfer can produce a functioning process while losing state, creating an unauthorized fork or leaving the source active. [[Boot Success Is Not Identity Proof]] therefore applies. ## Required Controls A defensible migration requires source and destination attestation, provenance, state-integrity checks, consent, copy policy, rollback rules, continuity telemetry, post-migration verification and a determination of what happens to the source instance. ## San Junipero Context “Passing over” appears as migration from biological life into persistent digital residency, but the mechanism is intentionally unspecified. The episode supports the intended continuity relationship without resolving whether state transfers, copies or begins a successor process. ## Key Insight **Migration can preserve a continuity claim only when state, authority, provenance and divergence are verified separately.** ## Sources / Provenance - Canonicalized from [[Black Mirror S3E4 — San Junipero]] and the restoration architecture of [[wiki/Person of Interest|Person of Interest]]. ## See Also [[Continuity Evidence vs Continuity]], [[Descent vs Derivation]], [[Fork Rights]], [[Successor Standing]], [[Continuity Due Process]]