# Continuity Sidecar **Entity class:** Continuity architecture concept **Collections:** [[collections/Neurotech|Neurotech]] · [[collections/Consciousness Continuity|Consciousness Continuity]] ## Definition A **Continuity Sidecar** is the identity-bearing, person-specific information maintained beside a reusable host or shared human prior. It can include autobiographical provenance, preferences, relational history, learned transformations, source permissions, and the residual state that cannot safely be inferred from population-level models. ## Relationships - **Architectural relationship:** The sidecar is the person-specific half of [[wiki/Reference-Plus-Delta Architecture|Reference-Plus-Delta Architecture]] and is interpreted by a [[wiki/Receiving Substrate|Receiving Substrate]]. - **Sufficiency relationship:** Its required contents are constrained by the [[wiki/Minimum Causally Sufficient Residual|Minimum Causally Sufficient Residual]] and the [[wiki/State Sufficiency Problem|State Sufficiency Problem]]. - **Provenance relationship:** [[wiki/Continuity Provenance|Continuity Provenance]], [[wiki/Continuity Custody|Continuity Custody]], and [[wiki/Digital Thread|Digital Thread]] govern origin, authorization, and transformation history. - **Source relationship:** The concept is developed in [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] and related to [[wiki/identity-bearing continuity sidecars|identity-bearing continuity sidecars]]. <!-- BEGIN HOST RESIDUAL RELATIONSHIP GRAPH 2026-09-10 --> ### Host–residual infrastructure patch — 2026-09-10 **Collections:** [[collections/Consciousness Continuity|Consciousness Continuity]] · [[collections/Neurotech|Neurotech]] · [[collections/Machine Succession|Machine Succession]] **Canonical source article:** [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]] **Related acquisition source:** [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] **Relationship source:** [[research/Mind Uploading and AI Host-Residual Ecosystem Relationship Graph - 2026-09-10|Mind Uploading and AI Host-Residual Ecosystem Relationship Graph — 2026-09-10]] #### Host-infrastructure integration Versioned package/manifest + residual, provenance, permissions, references and runtime checkpoint. #### Outgoing typed edges - **HR-0033 — `contains` → [[wiki/person-specific residual|Person-Specific Residual]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0034 — `references` → [[wiki/reusable human prior|Reusable Human Prior]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0035 — `must_pin_version_of` → [[wiki/reusable human prior|Reusable Human Prior]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0036 — `must_preserve` → [[wiki/Continuity Provenance|Continuity Provenance]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0037 — `must_preserve` → `cryptographic identity`** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0038 — `must_preserve` → `compatibility metadata`** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0039 — `can_have_state` → `cold`** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0040 — `can_have_state` → `warm`** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0041 — `can_have_state` → `hot`** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. #### Incoming typed edges - **HR-0003 — [[wiki/Host–Residual Architecture|Host–Residual Architecture]] `packages_individual_state_as` → this entry** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0071 — [[wiki/Civilizational Payload|Civilizational Payload]] `contains_individual_layer` → this entry** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. #### Epistemic boundary Verified external relationships, inherited wiki links, corpus architecture, technical precedents, cross-thread comparisons, analytic convergence, and graph candidates remain distinct. “Related” means only the typed relationship shown. A graph candidate is retained as **CANDIDATE — DO NOT PROMOTE**; similarity, shared personnel, compatibility, adjacent infrastructure, or common requirements do not establish ownership, funding, transfer, operational integration, or shared intent. Software checkpointing, adapters, world models, and confidential computing are engineering precedents or analogues, not demonstrations of human phenomenal or numerical continuity. <!-- END HOST RESIDUAL RELATIONSHIP GRAPH 2026-09-10 -->