# host-residual architecture **Entity class:** Technology, method, or technical system **Collections:** [[collections/Neurotech|Neurotech]] · [[collections/Consciousness Continuity|Consciousness Continuity]] ## Definition **Host–Residual Architecture** separates reusable civilization-scale structure from the state that identifies one person. The host supplies shared human and world models, reference systems, compute, memory, storage, embodiment, migration, identity, and interpretive services. A [[wiki/Continuity Sidecar|Continuity Sidecar]] supplies the [[wiki/person-specific residual|person-specific residual]], its dependencies, provenance, permissions, and current checkpoint. Re-instantiation joins those layers on a [[wiki/Receiving Substrate|Receiving Substrate]] through versioned [[wiki/Re-entry Pathways|re-entry pathways]]. The architecture makes the acquisition boundary explicit: computational sharing can reduce redundant representation, while the [[wiki/minimum causally sufficient residual|minimum causally sufficient residual]] remains unknown. ## Relationships <!-- BEGIN HUMANIZED RELATIONSHIPS 2026-09-11 --> This entry is routed through [[collections/Consciousness Continuity|Consciousness Continuity]], [[collections/Neurotech|Neurotech]], and [[collections/Machine Succession|Machine Succession]]. Its source context is developed in [[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]] and [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]]. Status-qualified source edges are preserved in the terminal Research Edges section. ### Key Relationships - **Host–Residual Architecture** includes [[wiki/reusable human prior|Reusable Human Prior]]. - **Host–Residual Architecture** includes [[wiki/person-specific residual|Person-Specific Residual]]. - **Host–Residual Architecture** packages individual state as [[wiki/Continuity Sidecar|Continuity Sidecar]]. - **Host–Residual Architecture** executes on [[wiki/Receiving Substrate|Receiving Substrate]]. - **Host–Residual Architecture** requires [[wiki/Re-entry Pathways|Re-entry Pathways]]. - **Host–Residual Architecture** requires [[wiki/Continuity Provenance|Continuity Provenance]]. - **Host–Residual Architecture** requires [[wiki/Runtime Coherence|Runtime Coherence]]. - **Host–Residual Architecture** requires [[wiki/Computational Metabolism|Computational Metabolism]]. - [[wiki/reference-plus-delta architecture|Reference-Plus-Delta Architecture]] provides a representation principle for **Host–Residual Architecture**. - [[wiki/Receiving Substrate|Receiving Substrate]] hosts **Host–Residual Architecture**. - [[wiki/Reconstructed Person|Reconstructed Person]] could be instantiated by **Host–Residual Architecture**. ### Governance, authority, and safeguards - **Host–Residual Architecture** is governed by [[wiki/Continuity Contract|Continuity Contract]]. - **Host–Residual Architecture** creates a governance problem concerning [[wiki/Platform Custody|Platform Custody]]. - **Host–Residual Architecture** creates a governance problem concerning [[wiki/Residual Sovereign|Residual Sovereign]]. ### Technology and research relationships - The technical comparison identifies a convergence: [[wiki/Stateful Runtime Environment|Stateful Runtime Environment]] converges technically with **Host–Residual Architecture**. - The technical comparison identifies a convergence: [[wiki/Microsoft Model System|Microsoft model system]] converges technically with **Host–Residual Architecture**. Very close software architecture analogue: durable harness/context/memory survives model substitution. - The source corpus interprets the relationship this way: [[wiki/Distributed Relational Compression|Distributed Relational Compression]] provides conceptual support for **host-residual architecture**. ### Connections in this corpus - [[wiki/Digital Twin Interoperability|Digital Twin Interoperability]] is connected in the corpus with **Host–Residual Architecture**. Shared world/reference semantics allow many residuals to enter the same host world. - [[wiki/OpenAI|OpenAI]] is connected in the corpus with **Host–Residual Architecture**. - [[wiki/NVIDIA|NVIDIA]] is connected in the corpus with **Host–Residual Architecture**. NVIDIA spans compute, rack fabric, context memory, world models, robotics, biology collaborations and AI-factory finance. - [[wiki/AWS|AWS]] is connected in the corpus with **Host–Residual Architecture**. AWS spans Trainium, stateful runtime, confidential execution, identity, networking and deep archival storage. <!-- END HUMANIZED RELATIONSHIPS 2026-09-11 --> ## Related Work in the Corpus <!-- BEGIN HUMANIZED CORPUS ROUTES 2026-09-11 --> - In [[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]], **VII. But a file is not a person** provides the narrative context for **host-residual architecture**: This gives a much better mental image than the old science-fiction picture of a brain being scanned into one enormous file. <!-- END HUMANIZED CORPUS ROUTES 2026-09-11 --> ## Research Edges <!-- BEGIN CONSCIOUSNESS MAPPING TRANSFER RELATIONSHIP GRAPH 2026-09-10 --> #### Consciousness mapping and transfer graph patch — 2026-09-10 **Collections:** [[collections/Neurotech|Neurotech]] · [[collections/Consciousness Continuity|Consciousness Continuity]] **Relationship source:** [[research/Consciousness Mapping and Transfer Ecosystem Relationship Graph - 2026-09-10|Consciousness Mapping and Transfer Ecosystem Relationship Graph — 2026-09-10]] **Related source articles:** [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] · [[articles/The Architecture of Continuity and Emerging Neuroinformatics Standards|The Architecture of Continuity and Emerging Neuroinformatics Standards]] · [[articles/2026 Annual Report on Brain-Computer Interfaces|2026 Annual Report on Brain-Computer Interfaces]] · [[articles/The Organic-Synthetic Brain Atlas|The Organic-Synthetic Brain Atlas]] #### Incoming typed edges - **Edge 643 — [[wiki/Distributed Relational Compression|Distributed Relational Compression]] `supports_conceptually` → this entry** — **ARTICLE_ANALYTIC**; evidence `ARTICLE_NEW`. Core architecture of the rebuilt article; treat as synthesis unless separately verified. <!-- END CONSCIOUSNESS MAPPING TRANSFER RELATIONSHIP GRAPH 2026-09-10 --> <!-- 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 Running composition of shared prior, sidecar, interpreter, runtime, provenance, embodiment and world. #### Outgoing typed edges - **HR-0001 — `composes` → [[wiki/reusable human prior|Reusable Human Prior]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0002 — `composes` → [[wiki/person-specific residual|Person-Specific Residual]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0003 — `packages_individual_state_as` → [[wiki/Continuity Sidecar|Continuity Sidecar]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0004 — `executes_on` → [[wiki/Receiving Substrate|Receiving Substrate]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0005 — `requires` → [[wiki/Re-entry Pathways|Re-entry Pathways]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0006 — `requires` → [[wiki/Continuity Provenance|Continuity Provenance]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0007 — `requires` → [[wiki/Runtime Coherence|Runtime Coherence]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0008 — `requires` → [[wiki/Computational Metabolism|Computational Metabolism]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0009 — `governed_by` → [[wiki/Continuity Contract|Continuity Contract]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0010 — `creates_governance_problem` → [[wiki/Platform Custody|Platform Custody]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0011 — `creates_governance_problem` → [[wiki/Residual Sovereign|Residual Sovereign]]** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. #### Incoming typed edges - **HR-0012 — [[wiki/reference-plus-delta architecture|Reference-Plus-Delta Architecture]] `is_representation_principle_for` → this entry** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0060 — [[wiki/Receiving Substrate|Receiving Substrate]] `hosts` → this entry** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0075 — [[wiki/Reconstructed Person|Reconstructed Person]] `could_be_instantiated_by` → this entry** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki. - **HR-0096 — [[wiki/Stateful Runtime Environment|Stateful Runtime Environment]] `technical_convergence_with` → this entry** — **ANALYTIC CONVERGENCE**; evidence `WEB_OPENAI_STATEFUL`, `ARTICLE`. Persistent state, memory, environment and identity are host-side primitives, not proof of continuity intent. - **HR-0104 — [[wiki/Microsoft Model System|Microsoft model system]] `technical_convergence_with` → this entry** — **STRONG ANALYTIC CONVERGENCE**; evidence `WEB_MS_MODEL_SYSTEM`, `ARTICLE`. Very close software architecture analogue: durable harness/context/memory survives model substitution. - **HR-1382 — [[wiki/Digital Twin Interoperability|Digital Twin Interoperability]] `cross_threads` → this entry** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Shared world/reference semantics allow many residuals to enter the same host world. - **HR-1416 — [[wiki/OpenAI|OpenAI]] `cross_threads` → this entry** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Same corporate ecosystem now spans stateful runtime, hyperscale compute and BCI investment; relationship is adjacency, not declared continuity intent. - **HR-1417 — [[wiki/NVIDIA|NVIDIA]] `cross_threads` → this entry** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. NVIDIA spans compute, rack fabric, context memory, world models, robotics, biology collaborations and AI-factory finance. - **HR-1420 — [[wiki/Amazon Web Services|AWS]] `cross_threads` → this entry** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. AWS spans Trainium, stateful runtime, confidential execution, identity, networking and deep archival storage. <!-- END HOST RESIDUAL RELATIONSHIP GRAPH 2026-09-10 --> ## Research Inferences <!-- BEGIN RESEARCH INFERENCES 2026-09-11 --> These entries translate the forward-looking register in [[research/Research Inferences|Research Inferences]] into ordinary wiki prose. The tier labels apply to the inference, not automatically to every factual anchor inside it. The interpretive frame comes from [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] and [[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]]. Collection route: [[collections/Neurotech|Neurotech]]. ### Continuity engineering: host and residual - **INF-0201 — Analytic.** Most of what a human brain encodes is species-general and reconstructible from population data; what is person-specific is comparatively small. Splitting the reusable prior from the person-specific residual turns an impossible acquisition problem into a tractable one, because only the residual must be measured. - **Attractor routes:** [[wiki/reusable human prior|reusable human prior]] · [[wiki/person-specific residual|person-specific residual]] - **INF-0202 — Plausible.** If the residual is the only thing that must be captured, the acquisition target shrinks by whatever fraction the shared prior explains. Estimating that fraction empirically — in mice first, through comparative connectomics — is the most consequential measurement in the entire continuity program. - **Attractor routes:** [[wiki/person-specific residual|person-specific residual]] · [[wiki/Compression|Compression]] - **INF-0203 — Unresolved.** The smallest state that reproduces a specific person's behavior and continuity of experience has no established size, and every claim about uploading feasibility is a hidden estimate of it. Resolution comes from progressive ablation studies on emulated animals, not from argument. - **Attractor routes:** [[wiki/minimum causally sufficient residual|minimum causally sufficient residual]] · [[wiki/person-specific residual|person-specific residual]] - **INF-0204 — Analytic.** Moving a residual onto a host requires a transform from biological representation to host representation, and that transform is learnable if paired data exists. Every decoding experiment that aligns brain activity to a model's latent space is producing fragments of that transform. - **Attractor routes:** [[wiki/transform function|transform function]] · [[wiki/Receiving Substrate|Receiving Substrate]] - **INF-0205 — Strongly indicated.** Storing a shared base plus a per-person delta is how every large software distribution system already works, and it is orders of magnitude cheaper than storing complete copies. Continuity infrastructure will converge on this pattern because the economics leave no alternative. - **Attractor routes:** [[wiki/reference-plus-delta architecture|reference-plus-delta architecture]] · [[wiki/reusable human prior|reusable human prior]] - **INF-0206 — Established.** Commercial AI systems became stateful in 2026, accumulating durable per-user context across sessions. The industry crossed from stateless tools to persistent relationships for product reasons, and persistence is the prerequisite property for anything resembling continuity. - **Attractor routes:** [[wiki/Continuity Provenance|Continuity Provenance]] · [[wiki/Receiving Substrate|Receiving Substrate]] - **INF-0207 — Analytic.** Retrieval-augmented systems separate a small working context from a large external store, which is structurally the hippocampal-neocortical division of labor. Systems converge on this architecture independently because the constraint — bounded fast memory, unbounded slow memory — is the same in both substrates. - **Attractor routes:** [[wiki/Memory Architecture|Memory Architecture]] · [[wiki/reference-plus-delta architecture|reference-plus-delta architecture]] - **INF-0208 — Plausible.** A sidecar that holds the person's state separately from the model that runs it makes the model replaceable without loss. Decoupling state from engine is the single design decision that determines whether a hosted person can ever change providers. - **Attractor routes:** [[wiki/Continuity Sidecar|Continuity Sidecar]] · [[wiki/Portability|Portability]] - **INF-0209 — Strongly indicated.** Frontier models are retired on cycles of months, which means any state bound to a specific model inherits that lifespan. Continuity across host turnover is therefore an immediate operational problem, not a distant one, and it is being encountered right now by users of persistent assistants. - **Attractor routes:** [[wiki/person-specific residual|person-specific residual]] · [[wiki/reusable human prior|reusable human prior]] - **INF-0210 — Plausible.** A fine-tuned adapter is a compact, portable encoding of person-specific behavior that rides on top of a general model. Adapters are the closest existing artifact to a residual, and they are already transferable between compatible base models. - **Attractor routes:** [[wiki/person-specific residual|person-specific residual]] · [[wiki/transform function|transform function]] - **INF-0211 — Plausible.** Distilling accumulated interaction history into a compact adapter would compress a person's residual the way consolidation compresses a day into memory. Both processes trade detail for durability, and both are lossy in ways the subject cannot audit. - **Attractor routes:** [[wiki/person-specific residual|person-specific residual]] · [[wiki/State Sufficiency Problem|State Sufficiency Problem]] - **INF-0212 — Strongly indicated.** Systems trained on a person's writing, speech, and decisions already produce convincing behavioral proxies without any neural measurement. The proxy route reaches practical utility long before the neural route reaches fidelity, which means the market will meet a functional simulacrum first. - **Attractor routes:** [[wiki/Continuity Provenance|Continuity Provenance]] · [[wiki/State Sufficiency Problem|State Sufficiency Problem]] - **INF-0213 — Analytic.** Distinguishing a behavioral proxy from a causally continuous person requires a test the proxy cannot pass, and no such test is currently specified. Specifying one is urgent precisely because proxies will be commercially available and emotionally satisfying before the distinction matters legally. - **Attractor routes:** [[wiki/Adjudication|Adjudication]] · [[wiki/minimum causally sufficient residual|minimum causally sufficient residual]] - **INF-0214 — Plausible.** Continuous capture of a person's sensory stream, communications, and decisions accumulates the training corpus for their own residual without any invasive procedure. The cheapest path to a person-specific model runs through ordinary consumer telemetry, and it is already partially collected. - **Attractor routes:** [[wiki/person-specific residual|person-specific residual]] · [[wiki/minimum causally sufficient residual|minimum causally sufficient residual]] - **INF-0215 — Analytic.** Everything a person emits — keystroke dynamics, gaze, gait, voice prosody, purchase timing — is peripheral evidence of internal state. A sufficiently large peripheral record constrains the internal model enormously, which makes non-neural data a continuity asset that no neural privacy law currently touches. - **Attractor routes:** [[wiki/Continuity Provenance|Continuity Provenance]] · [[wiki/reusable human prior|reusable human prior]] - **INF-0216 — Plausible.** A hosted state will need to prove it is the continuation of a particular person, which is an authentication problem with cryptographic solutions. Signing checkpoints with keys held by the person during life is the simplest available mechanism and requires no new technology. - **Attractor routes:** [[wiki/Continuity Provenance|Continuity Provenance]] · [[wiki/Psychological Continuity|Psychological Continuity]] - **INF-0217 — Strongly indicated.** An unbroken, signed record of every transformation applied to a person's state is the only way a future adjudicator could evaluate a continuity claim. Provenance chains must be started before they are needed, which makes the recording discipline urgent while the technology is immature. - **Attractor routes:** [[wiki/Continuity Provenance|Continuity Provenance]] · [[wiki/Continuity Sidecar|Continuity Sidecar]] - **INF-0218 — Analytic.** Any checkpointing scheme defines a maximum amount of experience that can be lost, and for a person that window is measured in memories rather than transactions. Choosing a cadence is choosing how much of a life is expendable, which is a decision no operational document currently frames as such. - **Attractor routes:** [[wiki/person-specific residual|person-specific residual]] · [[wiki/Receiving Substrate|Receiving Substrate]] - **INF-0219 — Unresolved.** Two instances started from one checkpoint diverge immediately and irreversibly, and no framework specifies which holds the original's obligations or entitlements. The question becomes practical the first time a backup is restored while the original is still running. - **Attractor routes:** [[wiki/reference-plus-delta architecture|reference-plus-delta architecture]] · [[wiki/Continuity Provenance|Continuity Provenance]] - **INF-0220 — Plausible.** A hosted state whose provider fails, is acquired, or exits the business is stranded in a format only that provider could interpret. Escrow of both state and interpreter is the elementary protection, and it is standard practice in enterprise software licensing already. - **Attractor routes:** [[wiki/Continuity Orphan|Continuity Orphan]] · [[wiki/Continuity Provenance|Continuity Provenance]] - **INF-0221 — Analytic.** Whoever holds privileged access to the substrate can read, modify, pause, or copy a hosted state, and no property of the state itself constrains that. The operator's privilege level is the real location of power in any continuity architecture, which is why attestation and enclaves matter more than contracts. - **Attractor routes:** [[wiki/Ring Zero|Ring Zero]] · [[wiki/Receiving Substrate|Receiving Substrate]] - **INF-0222 — Plausible.** Suspending a process costs nothing and is reversible, which makes indefinite suspension the cheapest disposition of an inconvenient hosted mind. Cost asymmetry between running and storing is the structural pressure that any governance regime must counteract deliberately. - **Attractor routes:** [[wiki/reusable human prior|reusable human prior]] · [[wiki/Continuity Provenance|Continuity Provenance]] - **INF-0223 — Strongly indicated.** A hosted mind consumes power continuously, so its persistence depends on a funding relationship that must outlive the person's earning capacity. Endowment structures, insurance products, and perpetual trusts are the financial instruments this requires, and all three already exist. - **Attractor routes:** [[wiki/Receiving Substrate|Receiving Substrate]] · [[wiki/person-specific residual|person-specific residual]] - **INF-0224 — Analytic.** An SLA that specifies uptime, restore-point objective, and data durability is, for a hosted person, a specification of how much death is contractually acceptable. Existing enterprise contract language would perform that function unmodified, which is exactly why it will be used. - **Attractor routes:** [[wiki/transform function|transform function]] · [[wiki/Receiving Substrate|Receiving Substrate]] - **INF-0225 — Plausible.** If the residual format is open and documented, hosts compete on quality; if proprietary, the first mover holds every customer permanently. This is the same fight as document formats and messaging protocols, with the same dynamics and vastly higher stakes. - **Attractor routes:** [[wiki/minimum causally sufficient residual|minimum causally sufficient residual]] · [[wiki/person-specific residual|person-specific residual]] <!-- END RESEARCH INFERENCES 2026-09-11 --> ## Quotations <!-- BEGIN VERIFIED QUOTATIONS 2026-09-11 --> Quotations here are evidence for named propositions, not substitutes for proof. Confidence grades describe the quotation's provenance; they do not raise the associated scientific or philosophical inference to the same tier. The selection record is [[research/Research Inferences|Research Inferences]] and the supplied quotation review dated 2026-09-11. > “We are not stuff that abides, but patterns that perpetuate themselves.” > > — **Norbert Wiener**, The Human Use of Human Beings (1950). [Source](https://library.agnescameron.info/cybernetics/The%20Human%20Use%20of%20Human%20Beings%2C%20Norbert%20Wiener%20%281950%29.pdf) · **Provenance confidence:** Medium **Evidentiary role:** provides a historical ancestor for pattern-based continuity claims. <!-- END VERIFIED QUOTATIONS 2026-09-11 --> ## Linked News Entries - [[news/Human Brain Grows from Two Ancient Nervous Systems|Human Brain Grows from Two Ancient Nervous Systems]] — the two-progenitor finding implies the host/delta boundary and sufficiency accounting may need to respect the developmental seam.