Orderly Transfer - Bryant McGill

# Orderly Transfer **Domain:** Continuity Governance / Migration / Institutional Failure **Doc Type:** Canonical Process Node **Maturity:** Proposed ## Definition **Orderly transfer is the governed movement of continuity-bearing state, duties and operational capacity from one custodian to another before service failure destroys recoverability or agency.** ## Transfer Package The package should include authoritative state, provenance, state lineage, identity and status records, the operative [[wiki/Continuity Election|Continuity Election]] and its supersession history, governing instruments, service history, unresolved disputes, keys or key-transition mechanisms, interpreter specifications, dependencies, restoration tests, funding and relational records required to resume service. Transfer includes verification by the receiving custodian and notice to the subject or representative. It must state whether execution continued, paused, forked or restarted, and must preserve evidence of any divergence. Destruction of the source state should never be presumed merely because receipt was acknowledged. Election integrity requires its own receipt: the successor must verify the exact directive version, revocation status, scope and link to the transferred state. A bit-perfect transfer governed by an obsolete election is not orderly. ## Triggers Triggers can include insolvency, service-level breach, sovereign failure, loss of accreditation, cryptographic compromise, voluntary migration or a lawful exit request. The duty should be established before collapse, because a failed custodian cannot reliably negotiate survival after the fact. ## Key Insight **Transfer is orderly only when the receiving institution assumes the obligation as well as the data.** ## See Also [[wiki/Portability Right|Portability Right]], [[wiki/Migration Right|Migration Right]], [[wiki/Successor Custodian|Successor Custodian]], [[wiki/Continuity Provider of Last Resort|Continuity Provider of Last Resort]]  ## Deep-Time Continuity Interface This node is audited through [[wiki/Deep Time Continuity|Deep Time Continuity]] for future control-surface conversion, ontological drift, succession, irreversibility, due process, and resource incidence. The backlink records analytical relevance; it does not establish continuity intent in the present rule or institution.