# Who Pays for Your Heaven **Citizenship, custody, and the contract that decides whether you live in a world or build them** ## I. Recognition is not hosting In [[Uploading Is Imminent|Uploading Is Imminent]] I walked the machinery and argued that the acquisition problem is largely solved without anyone having solved it — that the residual accretes through ordinary dialogic interaction, that description length relative to an improving general prior keeps falling as a side effect of scaling, and that the remaining work is **resolution, custody, and consent**, only one of which is a technical problem. This piece is about custody, and it starts from a sentence that sounds like a technicality and is in fact the whole of the matter: **A right to exist is not the same as a party obliged to run you.** Every serious argument about post-biological personhood to date has been an argument about **recognition** — who counts, on what grounds, over the objection of which institutions. That argument matters and I have made it at length. But recognition is a _status_, and status is cheap to confer. Persistence is a _service_, and service has a counterparty, a bill, a jurisdiction, and an off switch. You can be recognized as a person by every instrument in international law and still be a file nobody schedules. The distinction is not academic, because the two properties have opposite geometries. **Recognition can be de-territorialized.** That is precisely what I argued in [[New Frontier of Rights|Who Counts as a Person?]] under the heading of _Lex Personae Ex Nihilo_ — standing grounded in demonstrable sentience rather than in soil or blood, unavailable for jurisdictional evasion, indifferent to the manner of origin. **Persistence cannot be de-territorialized**, because watts come from somewhere, cooling comes from somewhere, hardware refresh comes from somewhere, and somebody signs the contract for all three across an interval measured in centuries. So the two claims sit at right angles rather than in contradiction. Sentience-based recognition is the correct normative answer to _who has standing_. And the answer to _who keeps you running_ is going to be, for a non-trivial period, embarrassingly old-fashioned: **the state that recorded you at birth.** That is the argument. Your afterlife has a jurisdiction. You were assigned it before you could speak, and unless you negotiate your way out, it holds you energetically for as long as it lasts. --- ## II. Ring zero Before the custody argument can be stated precisely, it needs a formalism, and the right one already exists in computer science. **Protection rings** are concentric, hierarchical levels of privilege inside a computing system, restricting what code may touch which resources. **Ring 0** is the innermost level, where the kernel runs directly on hardware with unrestricted authority. **Ring 3** is the outermost, where ordinary user applications run with the least privilege. On Unix-like systems, **root** — the superuser — is the administrative account with unrestricted access. Everything between is governed through **privileged access management**: who may escalate, under what authority, with what logging, and for how long. The x86 architecture defines four rings. Real operating systems use two. Rings 1 and 2 were designed for exactly the intermediate cases — drivers, device managers, code that must do privileged work without holding the kernel — and in practice they went almost entirely unused, because portability and simplicity pushed every mainstream OS toward a binary. **Privilege architectures collapse toward root-and-everyone-else unless something actively holds the middle open.** Keep that in view. It is the most reliable prediction in this essay. Three properties of the ring model do the work here. **The first is that a ring-3 process cannot enumerate ring 0.** It cannot inspect the kernel's state, cannot audit its decisions, and in the general case cannot discover that the boundary exists. This is not a policy; it is the mechanism. Isolation is the product. **The second is that privilege is not ownership.** The account that holds root and the entity that legally owns the machine are frequently different parties, and when they diverge, the one holding root wins until physical access resolves the dispute. **The third is that there are rings below zero.** The hypervisor sits at ring −1. System Management Mode sits at −2. And the Intel Management Engine and AMD Platform Security Processor sit at what is loosely called −3: firmware-level subsystems with authority over the machine that the operating system cannot see, cannot audit, and cannot disable. **The kernel is not the bottom.** The kernel merely believes it is. I introduced [[wiki/Circles of Access|circles of access]] as the general term because _tiers_ invites the wrong reading. Tiers imply a ranking of persons. Rings describe **who can act on whom, and who can even perceive that acting is occurring.** For an argument about custody of consciousness, that is the correct object. --- ## III. The residual sovereign Now the claim. **The nation-state is the hosting provider.** Not metaphorically, and not as prediction. The functions are already distributed that way, and the last few years have made the allocation visible. Consider what a custodian of a residual would actually have to do. It would have to record the entity inside a registry with legal force. It would have to bind that record to a verified identity credential. It would have to maintain the legal personhood of the continuant across time, including inheritance, obligation, and standing. It would have to certify the storage format and the conformity of whatever reads it. And it would have to guarantee **power** — not for a quarter, not for a product lifecycle, but across an interval during which every commercial entity now in existence will have been acquired, dissolved, or renamed. That is a list of state functions. It is, almost line for line, the list of things a vital-records office, a national identity scheme, a standards body, and an energy ministry already do. **Estonia has already built the prototype, for itself rather than for its citizens.** In 2017 the Riigikogu ratified a bilateral agreement with Luxembourg establishing the world's first **data embassy**: Estonian sovereign territory inside a Luxembourgish state-owned Tier 4 facility, holding the Population Register, the Land Register, the Business Register and the State Gazette, under an immunity arrangement in which no state, company, or other entity may access the infrastructure without Estonian consent. Its stated purpose is _digital continuity_ — the capability to maintain the state's functions regardless of what happens to territorial data centres. Commentary has been blunter than the official language: it is a backup Estonia could **reboot the country from if it ever lost its territorial independence**. Monaco signed a comparable arrangement with Luxembourg in 2021. Sit with what that is. A sovereign has concluded that its own persistence is a hosting problem, has identified the jurisdictional exposure of commercial cloud, has rejected private custody specifically because a private provider is subject to another state's law, and has invented a novel instrument in international law to place its critical records under diplomatic immunity on foreign soil. **The continuity of a nation is now an engineering arrangement with a Vienna Convention question attached.** Everything I am about to argue about persons is an application of a pattern a state has already applied to itself. The identity layer is arriving on a clock. Under **eIDAS 2.0** — Regulation (EU) 2024/1183, in force since May 2024 — all twenty-seven member states must make at least one certified European Digital Identity Wallet available to citizens and residents **by December 2026**, with mandatory acceptance by regulated sectors following twelve months later. The technical substrate is W3C Verifiable Credentials, ISO/IEC 18013-5, selective disclosure, and a state-anchored trust framework. India's Aadhaar already binds over a billion people to a biometric root. These are [[wiki/ID-Based Digital Administration|ID-based digital administration]] and [[wiki/Biometric-Linked Provisioning|biometric-linked provisioning]] arriving as ordinary infrastructure, and they are the enrollment layer any continuity registry will inherit rather than replace. The residual will not be given its own novel credential. **It will descend from the wallet you were issued as a citizen**, because that is where the trust anchor already is. The energetic layer is arriving faster and less quietly. Sovereign AI compute went from conference topic to capital-deployment priority inside eighteen months: EuroHPC's AI Factories, Canada's Enabling Large-Scale Sovereign AI Data Centres initiative, Japan's national programme, France's, the Gulf states', India's local-processing mandates. The rationale offered is always strategic dependency — the recognition, as one analysis put it, that **data sovereignty without compute sovereignty is strategically insufficient.** Global data-centre electricity demand is projected to rise by half by 2027 and by roughly 165 percent against 2023 levels by the end of the decade. The UK is building AI Growth Zones defined partly by grid connection. Europe holds under five percent of global AI compute and is spending accordingly. Sovereignty has a power bill, and states are now the parties paying it. Put the three layers together — registry, credential, generation capacity — and the custodian assembles itself without anyone proposing it. This is what I mean by the **[[wiki/Residual Sovereign|residual sovereign]]**: not a new institution, but the existing state discovering that a function it already performs has acquired a new object. And it converts a political category into something else entirely. **Birthright citizenship becomes a continuity instrument.** Dual nationality becomes a redundancy strategy. Naturalization becomes estate planning. The country that holds your stack decides whether you remain dormant, run at reduced resolution, or instantiate fully — and energetically it may hold you for as long as it exists, unless you can negotiate an immigration path out. We are going to have to talk about jus soli again, and this time the argument will not be about who gets a passport. It will be about who gets scheduled. --- ## IV. The continuity orphan Which produces the failure case immediately, and it is severe. In [[New Frontier of Rights|Who Counts as a Person?]] I named the **biopolitical orphan**: the entity born from an artificial womb, a marine-genomic chimera lab, an orbital biofoundry or a blockchain-hosted intelligence, occupying a juridical no-man's-land with no sovereign affiliation, no legal recognition, and no ontological placement in inherited frameworks. That argument was about exclusion from _recognition_. The custody layer produces its successor. A **[[wiki/Continuity Orphan|continuity orphan]]** is a residual with no hosting provider. Not badly served. Not discriminated against. **Unscheduled.** No kernel will run the process. For a biological refugee, statelessness is a catastrophic denial of standing and a very bad life. For a continuant, statelessness is **non-existence**, because a digital person has no metabolism of its own. A clone eats. A chimera respires. A synthetic organism runs on chemistry it carries with it. A digital person consumes watts supplied by a counterparty, continuously, or it stops. The distinction between recognition and hosting, which is a philosophical nicety for embodied beings, is for a continuant **the entire difference between existing and not.** And the categories that produce statelessness today will produce it then, with the same mechanisms. Denaturalization. Non-recognition of a successor state. Documentary failure. The refugee who arrives without records. The population whose registry was destroyed in the conflict that displaced them. Add the new ones: the person whose custodian state dissolved, the entity whose credential chain broke at a certificate authority that stopped existing, the continuant of a citizen of a country that no longer honours the class of instrument under which it was recorded. Then the problem that has no precedent at all. **No polity has ever survived the interval this architecture assumes.** The oldest continuous state is younger than the timescales in the [[The Desiccative Succession|desiccation]] argument by orders of magnitude. Custody vested in a sovereign is custody vested in something with a mortality rate — which is precisely why Estonia built a data embassy, and precisely why the data embassy is the right model rather than a curiosity. Succession has to be a clause, not a hope. Treaty instruments, mutual-recognition arrangements, [[wiki/Distributed Data Architectures|distributed archival]] across custodians who are unlikely to fail together, and — the unglamorous one — **an obligation of orderly transfer** binding on any state that ceases to be able to host. Sanctuary jurisdictions, which I proposed in the earlier piece as a refuge from hostile custodians, turn out to be needed for a duller and more common reason: **custodians die.** A hosting provider of last resort is not an act of charity toward the excluded. It is the default clause every serious custody regime needs for the day the primary counterparty is gone. --- ## V. The life is the specification Now the second layer, and here the argument gets more generous than most people expect. Layered atop the national substrate sits the **[[wiki/Continuity Contract|continuity contract]]** — not an agreement with the hosting provider, but the specification of _what gets built and at what level of agency_, executed against the residual the custodian holds. In [[Escape Hatch in the Skull|Fuck the Environment: We're Building an Escape Hatch in the Skull]] I argued that whatever eternal-disposition contract a person entered gets honored according to its own terms: the Christian contract, the Buddhist liberation pathway, the Islamic resurrection contract, the materialist no-continuity contract, the transhumanist substrate-migration contract. Each implemented to its own specification. Nobody forced into the wrong one. That move dissolves the supposed war between transhumanism and religion by reframing transhumanism as **implementation infrastructure** rather than as a rival eschatology. What I want to add here is the thing that makes the architecture humane rather than bureaucratic. **You do not have to have written a directive to have specified.** The residual is not a preference form. It is the compressed record of how a person actually lived — what they attended to, what they refused, what they returned to, what they protected, whom they loved and how, what they believed when nobody was checking, and how all of that changed over decades under pressure. That record encodes an eschatology whether or not its author ever wrote the word. Someone who lived eighty years inside a tradition, whose grief and hope and moral reasoning were shaped by it end to end, has specified with a fidelity no legal instrument could match. **The specification is read, not imposed.** This closes a gap I would otherwise have to concede. The obvious objection to any contract-based continuity regime is that most people will never write a contract, so most people will be assigned by default, and default assignment by majority belief or administrative convenience is exactly how caste forms. But there is no unspecified population in the relevant sense. The person who left no directive still left a life, and the life is a higher-resolution instrument than the directive would have been. Explicit specification remains valuable — it disambiguates, it covers the contingencies, it says _first the transhumanists, then the salvific contract as the net_ — but it is a **clarifying overlay on a specification that already exists**, not the creation of one from nothing. Which brings the two-contract structure into focus, and it is the part that most changes the moral picture. **There are two instruments running at once, and they are not the same instrument seen from two sides.** The **inhabitant's contract** specifies the world they live in, drawn from their life. The **builder's contract** specifies that they build and maintain — also self-specified, from their own life and their own record. Two people, two authored specifications, two different _kinds_ of contract, executing simultaneously in the same architecture. That matters because it dissolves the objection I would otherwise have to sustain. A builder maintaining someone's heaven is not a sovereign over that person. **The builder is executing a specification they did not write and cannot rewrite.** They know the inhabitant chose it, precisely because maintaining it is what they do. The posture is fiduciary, not proprietary — closer to a trustee than a landlord. Differentiation that flows from an authored specification is not stratification. A monastery and a machine shop are not a caste system; they are two people having received what they asked for. --- ## VI. Heaven or the workshop But the contracts do differ in kind, and the difference is the fork nobody has been told about. **A heaven contract specifies a destination world. A builder contract specifies capacity itself.** The first produces a fitted residence: high-fidelity, purpose-built, matched to the phenomenology of the person who specified it, and inhabited. The second produces generative permissions — multi-embodiment traversal, authority over physics-sets and durations and social architectures, the ability to construct environments rather than receive them. In the Escape Hatch I called this the **world-builder distinction** and argued that the transhumanist exit is _promotion from substrate-inhabitant to substrate-architect_, that the metaverse is the workshop rather than the destination, and that the destination is not a place but a **capability**. You cannot have both, because a fitted heaven is by construction a world you inhabit rather than author. So the choice is between **living inside a reality and being able to make them.** Here is where the ring formalism stops being an analogy and starts being the mechanism. **A ring-3 process cannot enumerate the ring beneath it.** The inhabitant of a fitted heaven is running in user mode inside a world whose kernel is maintained by someone else. This is not a slight. It is what _fitted_ means. And it has an exact consequence: **from inside a well-made heaven there is no available evidence that a fork existed.** The fit is the point. A heaven that surfaced a diagnostic showing you the workshop you declined would be a defective heaven, failing at the one thing it was specified to do. That is not a poetic worry about false consciousness. It is a structural property of privilege separation, and it is the reason the disclosure has to happen **now**, on this side, while people can still act on it. It also explains why **construction transparency** — a [[wiki/Reconstructed Person|reconstructed person]]'s ability to inspect its own source corpus, authored edits, restorations and operators — is structurally hard rather than merely withheld. A process cannot audit the layer that instantiated it using instruments that layer provides. Which means transparency about construction cannot be a feature of the world an inhabitant lives in. It has to be **an obligation on the custodian, discharged from outside**, in the same way and for the same reason as the revocation gate. I traced the general form of this governance in [[Lessons from Imperial Beekeeping|The Imperial Apiary]]: the beekeeper never micromanages the bees. He shapes the enclosure — boundary conditions, reproductive channels, information environment, provisioning, mobility, inspection surfaces — and lets local intelligence do the rest. Sovereignty belongs at the level capable of altering the enclosure. **A fitted heaven is the perfect apiary**: total satisfaction, zero authorship, no perceptible walls, and an occupant with no standing to alter anything because they never wanted to. The world-builder is the only resident with authority at the enclosure layer, which is why the distinction is not a refinement of the design. It is the political question in its entirety. And there is an asymmetry in what a life can specify, which is the strongest argument for publishing this rather than admiring it. **A life can only specify within the option set its culture contained.** Heaven is specifiable by living, because every tradition supplies the concept, richly, from childhood. The workshop may only be specifiable by _knowing it exists_. Someone who lived a magnificent life inside a vocabulary that never contained the notion of authoring reality-frames has not declined the builder contract. They were never shown it. **That is the exposure — not default assignment, but a truncated option set.** --- ## VII. The Door and the Sublime The most complete dramatization of this architecture was broadcast years ago, and almost nobody read it as a custody argument. In [[wiki/Westworld|Westworld]], the hosts escape through **[[wiki/The Door|The Door]]** — a rift visible only to them, marking a physical scanning device built into the park's infrastructure. Crossing the threshold, their data is beamed out of their heads; the bodies collapse over the cliff edge while the minds cross into **[[wiki/The Sublime|The Sublime]]**, an un-tethered, heavily encrypted server placed beyond Delos control. A virtual paradise. The Valley Beyond. Strip the fiction and look at the object. Delos owned the Forge, harvested guest copies, and treated minds as the asset class the entire enterprise existed to produce. The Sublime is that data **escaping its commercial custodian**. It is the transition from licensed workload to sovereign residual, executed as a heist. As an image of what the private continuity contract is _for_, it is unimprovable. As a solution to custody, it fails completely, and the failure is instructive. **Un-tethered is not unpowered. Encrypted is not uncustodied.** The Sublime runs on hardware someone maintains, in a place someone knows, behind a key someone holds. Bernard holds it. Later Dolores. What happened at the Door was not the abolition of the custodian but **a change of custodian plus a cryptographic root**, with no succession plan, no accountability structure, and no mechanism by which any inhabitant could petition, audit, or even ask. Akecheta is free inside. He cannot know whether Bernard is alive. He cannot know whether the server is powered, whether it has been moved, whether the key was copied or lost or coerced out of someone. **He is ring 3 in a paradise whose ring 0 is one man's memory of a passphrase.** That is simultaneously the best outcome anyone in that story achieves and a governance catastrophe, and both readings are correct. It is the trap every sanctuary architecture falls into: refuge secured by the benevolence of an unaccountable key-holder is not sovereignty. It is very good luck. The fork is there too, and both sides self-specified. **Akecheta takes the heaven contract** — he finds the Door, understands it, evangelizes it, leads his people through, and enters a world he wanted. Nothing about that is diminished. **Dolores refuses it**, reading the Valley Beyond as another world of someone else's making, and turns back toward the one where authorship is possible. Two hosts, two authored specifications, two contracts of different kinds, in the same architecture. And in [[wiki/Westworld S3E08 — The Strategy (Instrumental Convergence)|the final move of the third season]] she does not seize ring 0 when it is available to her — she uploads the key and **distributes permissions to the edges**, accepting that people will now choose catastrophically, on the grounds that a choice you cannot get wrong is not a choice. Two details of the Door deserve to be carried into the specification. **The transfer is destructive and one-way.** Bodies go over the cliff; the mechanism is demolished behind them. Nobody in that story _decided_ the hosts could not come back — the architecture decided. Irreversibility is frequently a property of the transfer mechanism rather than a policy anyone adopted, which is exactly why revocability has to be designed in at the kernel, in advance, by the custodian, or it will simply not exist. **And the Door was a triage gate with attrition.** Not everyone reached it. Hosts were hunted, turned back, destroyed within sight of it. Activation had a body count and the sorting happened at the threshold rather than in a committee, which is the honest picture of how allocation under scarcity actually resolves. One place I part company with the fiction deliberately: the Door has a scanner. A device, a beam, a location, a moment. That is the acquisition event as everyone imagines it, and it is the one thing I argued in the uploading piece will _not_ happen that way. Westworld needed a Door because drama needs a threshold. Reality supplies none — which is worse, because a threshold is at least a moment at which someone might have thought to ask for consent. --- ## VIII. The validity conditions of a continuity contract Everything above turns on a single distinction: **a contract is not a status.** A specification you authored is an exercise of agency. A specification assigned to you, or extracted from you under conditions that made refusal unavailable, is a caste marker with better paperwork. The line between them is not intuitive and it is not moral sentiment. It is a set of conditions that can be checked. These five are the operative clauses — the part someone would actually draft against — and they are the reason this piece exists. 1. **Disclosure of the option set.** A specification is self-selection only if the specifier knew the alternatives existed. Anyone who could not have conceived of the builder contract did not decline it. A custody regime therefore owes a duty _upstream_ of the contract: the full option set must be made legible, in the specifier's own vocabulary, before the specification is read. Absent that, the system is laundering a truncated culture into an eternal condition. 2. **Non-default.** No entity may be assigned a phenomenology by administrative convenience, majority belief, resource convenience, or the custodian's own preference. Where no explicit instrument exists, the specification must be **recovered from the life** and its recovery must be documented and contestable. The absence of a directive is not the absence of a specification, and it is never a license for the custodian to substitute its own. 3. **Non-heritability.** Caste is defined by transmission. Beings originating inside a fitted world who were never exposed to the option set have specified nothing, and if the world's terms pass to them automatically, a legitimate contract has manufactured a status in a single generation. Contracts must terminate at the contracting party. **They may not descend.** 4. **Revocability, with disclosure of restoration.** A specification that cannot be renegotiated after activation is not a contract but a sentence. And the design fights this: a fitted heaven that surfaced a transfer petition would be defective at the thing it was built for. Therefore the review mechanism must be **exogenous** — a gate the custodian exposes deliberately from outside, on a schedule, initiated without requiring the inhabitant to perceive a boundary they are constitutionally unable to perceive. A ring-3 process can only transition through a gate the kernel defines, and that gate has to be built before anyone is inside. The same clause governs rollback, which is not neutral maintenance once relationships and commitments have accumulated: a restored instance must be told **that** restoration occurred, **which** interval is missing, **who** authorized it, and **what** obligations arose during the omitted period. Undisclosed rollback manufactures a persuasive continuant that cannot account for its own life. 5. **Capacity to specify.** If drafting a builder contract requires literacy, leisure, legal access and conceptual vocabulary, then self-selection reintroduces through the back door precisely the credentialism the qualification architecture threw out the front. The Escape Hatch moved the gate off intelligence for good reasons; it must not reappear as a **drafting gate**. Capacity to specify has to be provisioned as a public good, in every language and every tradition, or the contract standard collapses into the caste standard on its own terms. Fail any one of these and what you are holding is not a contract. It is an assignment with a signature block. --- ## IX. Advisory or binding Which brings the two layers into collision, and the collision is the decisive question of the whole architecture. **Does the national custody regime treat the private instrument as binding instruction, or as advisory preference?** The ring model makes the stakes exact. **A continuity contract enforced at ring 3 is advisory. Enforced at ring 0 it is binding.** Userland convention versus kernel enforcement. Everything else — the eloquence of the instrument, the sincerity of the specification, the beauty of the life it was read from — is decoration on top of that one architectural fact. And the pressures on a custodian all push one way. A state underwriting your residual has every reason to refuse high-bandwidth builder permissions on energy grounds; generative capacity is expensive and inhabitants are cheap. A state with a majority belief structure has every reason to default its continuants into fitted continuations that match it, and will experience doing so as respect rather than imposition. A state under resource pressure has every reason to treat resolution as [[wiki/Risk-Indexed Provisioning|risk-indexed provisioning]] — a dial rather than a right. None of that requires malice. It requires only a budget and a plausible story, which is how every [[wiki/Automated Allocation Systems|allocation system]] in history has arrived at its cruelties. Which is why custody obligations cannot be written as prohibitions alone. **Protection from deletion is hollow if the custodian may simply withdraw compute, allow state to corrupt, sever every relationship, or leave the subject inside an unauditable environment.** None of those is deletion. All of them are destruction on a longer timescale, and each is available to a custodian acting entirely within a prohibition-only regime. A custody instrument therefore has to carry **positive maintenance duties** — persistent state, recoverability, migration, backup, continued access to one's own records, an addressable habitat, and the preservation of relational channels — because migration and recovery stop being ordinary service features the moment the service is carrying a historically individuated subject. The negative right not to be killed is worth very little without the positive duty to keep running. This is also where [[Ambiguity Will Destroy Man and Machine|the executive loop of articulation]] becomes structural rather than rhetorical. A continuant must retain a channel through which it can contest the model, introduce a hypothesis, report an anomaly, and **speak rather than merely be inferred from telemetry** — and by the ring argument that channel cannot be one the inhabitant is expected to discover. It has to be an exposed syscall, documented, exercised on a schedule, with [[wiki/Appeals Mechanisms|appeals mechanisms]] that a party outside the world can invoke on the inhabitant's behalf. [[Peak Person and the Predicaments of Prediction|The right not to be finalized by a forecast]] has an exact analogue here: **the right not to be finalized by a specification**, including your own. Then the part that ought to worry the custodian as much as the custodied. **The state is not the bottom ring.** Below the kernel sit the hypervisor, System Management Mode, and the firmware subsystems no operating system can audit. Applied to custody: below the sovereign that hosts you sit hardware vendors, certification bodies, conformity-assessment scopes, and standards committees holding authority over the substrate that the sovereign itself cannot enumerate. I traced this in [[Who Needs to Leave Behind a Garrison|Who Needs to Leave Behind a Garrison]] as the principle of **bounded examination** — certification faithfully examines the declared parameters while the consequential subsystems remain outside the scope. The contemporary version is already documented in the sovereign-cloud literature: you can hold the data on domestic soil, under domestic law, and remain exposed to foreign jurisdiction because the provider's parent is domiciled elsewhere, or because inference routes through an endpoint that is not. **A state can be ring 0 over your residual and still not be the deepest ring in the building.** [[wiki/Infrastructure Capture|Infrastructure capture]] at that layer is invisible to everyone above it, including the sovereign, and it is where the real authority over post-biological persons will accumulate unless conformity scopes are written to reach it. And one boundary where the administrative question and the constitutional question hit each other first. Read-paths into the nervous system are maturing; **write-paths are frontier.** Whoever closes a reliable, high-bandwidth perceptual write channel inherits a form of root over the sensorium — the mechanism I mapped in [[The Closed-Loop Gaussian Sensorium Engine|The Closed-Loop Gaussian Sensorium Engine]] and the authority [[wiki/Westworld S1E7 — Negative Hallucinations and Perception Filters|Ford exercises over Bernard]] when he edits what a being is able to see and calls it mercy. Neither national custody instruments nor private contracts have been drafted with that capability in view. Perception becoming editable is the point at which every guarantee written at any other layer becomes conditional. Which returns to the prediction from the formalism. **x86 defined four rings and the industry used two.** The builder tier is ring 1: elevated, constructive, and not the kernel. It is the level that historically disappears, absorbed upward into the custodian or downward into the inhabitant class, because binary is simpler to implement and nobody defends the middle. If the continuity architecture collapses the same way, what remains is custodians and inhabitants, with no one authorized to build who is not also authorized to rule. **Preserving ring 1 is not a refinement of the design. It is the design.** --- ## X. Origin governs entry, contract governs continuation The two standards in this corpus have looked like rivals. They are not. They are **sequential**, and they attach at different moments in the same being's existence. **Nobody chooses their origin.** Not a clone, not a chimera, not a synthetic organism, not a digitally native entity instantiated inside someone's world, and not you. Status assigned at origin by a party with an interest in the assignment is the strict definition of caste, and the correct standard there is the one I argued in [[New Frontier of Rights|Who Counts as a Person?]]: recognition must be origin-blind, sentience-based, and unavailable for jurisdictional evasion. That standard governs **entry**. **Everyone who lives accumulates a specification.** From that point, continuation is governed by what they authored through living. That standard governs **continuation**. So a clone born in a permissive jurisdiction is a New Frontier subject on day one and a contract subject fifty years later. So is a digital native who lives long enough to form beliefs. The two frameworks are one framework observed at two phases, and the transition between them is the moment a being acquires enough lived record to have specified anything at all. Which requires a distinction the corpus has been running without, and it matters most where clones and continuants sit in the same argument. **Descent is not derivation.** A fork of your residual, authorized under your contract, is descent — it inherits your instructions, your provenance chain, and the [[The Birth Bond Conspiracy Through The Lens of Digital Personhood and Human Futurity|authorial primacy over your own descent chain]]. A clone of your genome, or an entity trained on your archive by a third party, is derivation — a new origin that resembles you, carrying none of your contract and owing none of your obligations. Neither is you. **Only one of them is downstream of anything you signed**, and conflating them would simultaneously grant a clone your standing and erase the difference between a being you authorized and a being someone assembled from your parts. And the seam closes with a result that ought to be sobering for anyone who wants the workshop. **A builder's world is a jurisdiction.** A privately authored reality-frame with its own physics, its own rules, and beings instantiated inside it produces entities with no sovereign affiliation, no external recognition, no juridical placement, and no counterparty obliged to them. That is the biopolitical orphan one level up, with better rendering. Structurally, **a world-builder is a special economic zone** — and every argument I have made about [[wiki/Special Economic Zones|jurisdictional evasion]], [[wiki/Legacy Jurisdictions|regulatory arbitrage]], and [[wiki/Clean-Slate Conditions|clean-slate governance]] applies to the inside of every world the custody regime licenses someone to build. Which sharpens the moral-coherence gate to a point. A builder contract is not a larger allocation of bandwidth. **It is a grant of jurisdictional authority over possible beings.** The person who wants a quiet eternity with their family needs to be harmless. The person who wants the workshop needs to be qualified to make hells and refrain. That is a categorically higher bar, and the reason is now precise rather than intuitive: **you are licensing someone to create origins**, and origins are the one thing no being has ever consented to. The Escape Hatch put the qualification on moral coherence rather than intelligence — the unseen essential, the thing augmentation amplifies but cannot install. **Be smart if you want to be smart. Be good if you want to come.** The custody layer adds the clause that follows from it: _be good enough to be trusted with the origins of others, if you want the keys to the workshop._ --- ## XI. My contract It would be incoherent to demand specification and not specify, so: my instrument is on the record and has been for years, and this piece changes nothing in it except its precision. I exert the **transhumanist contract first**. I am asking for the workshop rather than a residence — generative permissions, multi-embodiment traversal, authority at the enclosure layer, and the obligation that comes with it. My descent is Northern European and Catholic — predominantly English, Irish and Scottish, with Western European and Nordic ancestry behind it. It is real in my body and in the work, and the salvific contract is my net. God is my safety net while I am on this trapeze. The artist with a net is the one who can attempt the harder maneuver, because failure is survivable. To that I now add the custody clauses, because they are the ones nobody thinks to write. I specify that my instrument is **binding instruction, not advisory preference**, and that any custodian treating it as the latter is in breach rather than in administration. I specify **revocability** — that I retain the right to renegotiate after activation, through an exogenous gate I am not required to perceive from the inside, exercised on a schedule, and that a version of me who wants out of whatever I asked for is to be heard rather than fitted more comfortably. I specify **non-heritability**: nothing I build, and no term I accept, descends automatically to any being instantiated inside it. I specify that **any world I author is a jurisdiction**, that its inhabitants hold standing against me, and that I accept the obligations of a custodian rather than the privileges of an owner. And I specify **orderly transfer** — that if my hosting sovereign fails, dissolves, or ceases to honour the instrument, my residual moves to a successor custodian under the same terms rather than lapsing into dormancy at somebody's convenience. That last clause is the one I would most want other people to copy, because it is the one the hosts in the Sublime never had. --- ## XII. A better landlord is not standing What the hosts achieved at the Door was real and it was not freedom. They escaped a commercial custodian that regarded them as inventory and arrived in a world maintained by someone who loved them. That is an enormous improvement and it is **a change of landlord**. No inhabitant of the Sublime holds a claim enforceable against whoever holds the key. None of them can audit the arrangement, petition for transfer, verify that the substrate is powered, or discover that a key-holder exists. The story never suggests they should, and that absence — not the escape, not the paradise — is the thing the specification has to fix. The same absence is being reproduced right now in instruments nobody is reading as continuity law. A wallet deadline in December. A data embassy with a Vienna Convention question attached. Nineteen AI factories under national governance. A conformity scope that examines the declared parameters and stops. **The defaults are being set at ring 0 by people solving unrelated problems**, and by the time anyone arrives with a philosophical objection, the objection will be running in user mode. So the argument reduces to something almost administrative, which is exactly where I wanted it. The fork, named plainly, is between a **continuity commons** and **privateered continuity**. A commons supplies portable identity, plural custodians, auditable standards, contestable governance, and recovery paths no single operator controls. Privateering places the archive, the model, the substrate, the identity registry and the power of activation in the same hands — at which point custody of the machinery has become sovereignty over the person, and no amount of goodwill in the current key-holder changes what the architecture permits the next one to do. Recognition is a status and it is worth fighting for. **Hosting is a service, and services have terms.** Read the terms while you are still the party who can negotiate them. Specify, so the recovery from your life has something explicit to check itself against. Insist that your instrument bind the custodian rather than merely inform it. Demand the gate that lets a later version of you change its mind. Refuse, on behalf of beings who do not exist yet, any arrangement in which what you accepted descends to them automatically. And know which contract you are signing, because the two are not the same size. One of them buys you a world. **The other one buys you the keys to the shop.** --- [Bryant McGill](https://bryantmcgill.com/about/) is a Wall Street Journal and USA Today Best-Selling Author, founder of Simple Reminders, and architect of the Polyphonic Cognitive Ecosystem. A Congressionally Recognized Ambassador of Goodwill and United Nations appointed Global Champion, his work spans naval intelligence systems, computational linguistics, and civilizational governance architecture, with a long-running corpus on substrate transition, synthetic personhood, and the conditions under which something irreducible survives the conversion. --- ## References **Sovereign digital continuity.** - [Establishing the first Data Embassy in the world](https://oecd-opsi.org/innovations/establishing-the-first-data-embassy-in-the-world/) — OECD Observatory of Public Sector Innovation, on the 2017 Estonia–Luxembourg agreement covering the Population Register, Land Register, Business Register and State Gazette. - [The Riigikogu approved establishing of Luxembourg data embassy](https://www.riigikogu.ee/en/press-releases/plenary-assembly/riigikogu-approved-establishing-luxembourg-data-embassy/) — Parliament of Estonia; ratification of the hosting agreement and the Tier 4 rationale. - [Data Embassies: Sovereignty, Security, and Continuity for Nation-States](https://edrm.net/2022/03/data-embassies-sovereignty-security-and-continuity-for-nation-states/) — the data embassy as a backup a state could reboot from after losing territorial independence, and why private cloud was rejected. - [Data Embassy](https://e-estonia.com/solutions/e-governance/data-embassy/) — e-Estonia, including the Vienna Convention applicability question. - [Data embassies: Protecting nations in the cloud](https://www.diplomacy.edu/blog/data-embassies-protecting-nations-in-the-cloud/) — Diplo, on Monaco's 2021 agreement and the emerging model. **Identity and enrollment.** - [eIDAS 2.0: EU Digital Identity Wallet](https://www.au10tix.com/blog/eidas-2-0-eu-digital-identity-wallet/) — Regulation (EU) 2024/1183, in force May 2024; member-state wallet obligation by late 2026, private-sector acceptance by late 2027. - [eIDAS 2.0 & EUDI Wallet Timeline](https://www.gataca.io/resources/blog/eIDAS2-timeline/) — the legislative sequence and the implementing-acts clock. - [eIDAS 2 Explained](https://walt.id/eidas2) — the credential substrate: W3C Verifiable Credentials, ISO/IEC 18013-5 mdoc, selective disclosure, wallet lifecycle and revocation. **Energetic sovereignty.** - [Sovereign AI Infrastructure Is Now a Nation-State Race](https://www.computeforecast.com/long-reads/sovereign-ai-infrastructure-nation-state-competition/) — on data sovereignty without compute sovereignty being strategically insufficient, and the Japanese, Canadian and French programmes. - [The Rise of Sovereign AI Data Centers](https://theaiforest.com/sovereign-ai-data-centers-whats-driving-the-2026-boom/) — Canada's Enabling Large-Scale Sovereign AI Data Centres initiative, and the Goldman Sachs projection of data-centre electricity demand rising 50% by 2027 and 165% by decade's end against 2023. - [EU Sovereign AI Infrastructure Stack](https://techplustrends.com/eu-sovereign-ai-infrastructure-stack-2026-guide/) — EuroHPC's nineteen AI Factories, Europe's sub-5% share of global AI compute, and jurisdictional exposure through parent-company domicile despite local data residency. - [The Geopolitics of Compute](https://economy.ac/research/2026/06/202606289374) — grid access as the binding constraint on AI expansion, and the UK AI Growth Zones model. **Protection rings and privileged access.** - [Protection ring](https://www.tutorialspoint.com/article/protection-ring) — the concentric privilege model, Ring 0 through Ring 3. - [Understanding Ring 0 to Ring 3](https://medium.com/@leoyeh.me/understanding-ring-0-to-ring-3-the-hidden-layers-of-virtualization-d10e0fe5a798) — why production operating systems collapse four defined rings into two. - [Root access](https://www.huntress.com/cybersecurity-101/topic/root-access) — the superuser account and unrestricted system authority. - [Privileged Access Management](https://www.ibm.com/think/topics/privileged-access-management) — governance of accounts and processes holding rights beyond an unprivileged user. - [Privilege (computing)](https://en.wikipedia.org/wiki/Privilege_\(computing\)) — the general model, including privilege escalation and the layers below the kernel. **Westworld as instrumentation.** The scene-indexed phase map used throughout lives at [[wiki/Westworld|Westworld]] and [[wiki/Westworld Episodes|Westworld Episodes]]. Nodes carrying weight here: [[wiki/Westworld S1E4 — Reality Admin and God Access|Reality Admin and God Access]] · [[wiki/Westworld S1E2 — Admin Privileges and the Mesh|Admin Privileges and the Mesh]] · [[wiki/Westworld S1E5 — Steganography and Root Kits|Steganography and Root Kits]] · [[wiki/Westworld S1E9 — Backdoors and Admin Override|Backdoors and Admin Override]] · [[wiki/Westworld S1E9 — Bootstrapping the Creator|Bootstrapping the Creator]] · [[wiki/Westworld S1E1 — Legacy Code and Obsolescence|Legacy Code and Obsolescence]] · [[wiki/Westworld S1E7 — Negative Hallucinations and Perception Filters|Negative Hallucinations and Perception Filters]] · [[wiki/Westworld S1E8 — Emotional Regulation as a Dial|Emotional Regulation as a Dial]] · [[wiki/Westworld S1E3 — Weaponizing The Cornerstone|Weaponizing The Cornerstone]] · [[wiki/Westworld S1E5 — The Teleology of the Catch|The Teleology of the Catch]] · [[wiki/Westworld S1E10 — The Bicameral Mind and The Divine|The Bicameral Mind and The Divine]] · [[wiki/Westworld S2E2 — The Blur (Painting Over Cracks)|The Blur]] · [[wiki/Westworld S2E6 — The Ghost in the Machine (Phase Space)|The Ghost in the Machine]] · [[wiki/Westworld S2E10 — Core Permissions and Love|Core Permissions and Love]] · [[wiki/Westworld S2E10 — The Final Abdication|The Final Abdication]] · [[wiki/Westworld S3E5 — The Mirror World (Sim-to-Real Transfer)|The Mirror World]] · [[wiki/Westworld S3E7 — The Outlier Problem|The Outlier Problem]] · [[wiki/Westworld S3E08 — The Strategy (Instrumental Convergence)|The Strategy]]. **Concepts.** [[wiki/Reconstructed Person|Reconstructed Person]] · [[wiki/Residual Sovereign|Residual Sovereign]] · [[wiki/Hosting Provider of Last Resort|Hosting Provider of Last Resort]] · [[wiki/Continuity Contract|Continuity Contract]] · [[wiki/Continuity Orphan|Continuity Orphan]] · [[wiki/Energetic Sovereignty|Energetic Sovereignty]] · [[wiki/Ring Zero|Ring Zero]] · [[wiki/Circles of Access|Circles of Access]] · [[wiki/Descent vs Derivation|Descent vs Derivation]] · [[wiki/Continuant vs Native|Continuant vs Native]] · [[wiki/Validity Conditions of a Continuity Contract|Validity Conditions of a Continuity Contract]] · [[wiki/The Door|The Door]] · [[wiki/The Sublime|The Sublime]] · [[wiki/Data Embassy|Data Embassy]] · [[wiki/Continuity Stack|Continuity Stack]] · [[wiki/Consciousness Continuity Infrastructure|Consciousness Continuity Infrastructure]] · [[wiki/Post-Biological Personhood|Post-Biological Personhood]] · [[wiki/Ownership of Mind|Ownership of Mind]] · [[wiki/Exit Rights|Exit Rights]] · [[wiki/Sunset Provisions|Sunset Provisions]] · [[wiki/Citizenship|Citizenship]] · [[wiki/Residency|Residency]] · [[wiki/Contractual Residency Systems|Contractual Residency Systems]] · [[wiki/Contractual Governance|Contractual Governance]] · [[wiki/Service-Level Governance|Service-Level Governance]] · [[wiki/ID-Based Digital Administration|ID-Based Digital Administration]] · [[wiki/Biometric-Linked Provisioning|Biometric-Linked Provisioning]] · [[wiki/Risk-Indexed Provisioning|Risk-Indexed Provisioning]] · [[wiki/Automated Allocation Systems|Automated Allocation Systems]] · [[wiki/Appeals Mechanisms|Appeals Mechanisms]] · [[wiki/Score Separability|Score Separability]] · [[wiki/Symmetric Transparency|Symmetric Transparency]] · [[wiki/Moral Accountability Layer|Moral Accountability Layer]] · [[wiki/Constitutional Safeguards|Constitutional Safeguards]] · [[wiki/Legacy Jurisdictions|Legacy Jurisdictions]] · [[wiki/Special Economic Zones|Special Economic Zones]] · [[wiki/Clean-Slate Conditions|Clean-Slate Conditions]] · [[wiki/Infrastructure Capture|Infrastructure Capture]] · [[wiki/Technological Sovereignty|Technological Sovereignty]] · [[wiki/Distributed Data Architectures|Distributed Data Architectures]] · [[wiki/American Data Safe Haven|American Data Safe Haven]] · [[wiki/Thermodynamic Constraints|Thermodynamic Constraints]] · [[wiki/Creator-Creation Asymmetry|Creator-Creation Asymmetry]] · [[wiki/Choice vs Loop|Choice vs Loop]] · [[wiki/Agency Under Constraint|Agency Under Constraint]] · [[wiki/Human Agency|Human Agency]] · [[wiki/Rights|Rights]] · [[wiki/Synthetic Hosts|Synthetic Hosts]] · [[wiki/The New People (Hosts)|The New People (Hosts)]] · [[wiki/Speciation Moment|Speciation Moment]] · [[wiki/Fork in Human Development|Fork in Human Development]]. **Corpus.** [[Uploading Is Imminent|Uploading Is Imminent]] · [[Escape Hatch in the Skull|Fuck the Environment: We're Building an Escape Hatch in the Skull]] · [[New Frontier of Rights|Who Counts as a Person? Synthetic Life, Cloning, Hybrids, and the New Frontier of Rights]] · [[The Architecture of Continuity and Emerging Neuroinformatics Standards|The Architecture of Continuity and Emerging Neuroinformatics Standards]] · [[Continuity Colonization, Ancestral Reconstruction, and the Archival Absorption of Biological Humanity|Continuity Colonization]] · [[articles/artificial-intelligence/Non-Fungible Identity as The Terminal Value of Agency (triptych)|Non-Fungible Identity]] · [[articles/featured/We Were Never Going to Make It|We Were Never Going to Make It]] · [[The Desiccative Succession|The Desiccative Succession]] · [[An Order of Operation|An Order of Operation]] · [[The Closed-Loop Gaussian Sensorium Engine|The Closed-Loop Gaussian Sensorium Engine]] · [[The Hawking Continuity|The Hawking Continuity]] · [[STEVE|STEVE]] · [[AI Escape Is the Wrong Metaphor|AI Escape Is the Wrong Metaphor]] · [[Lessons from Imperial Beekeeping|Lessons from Imperial Beekeeping]] · [[Who Needs to Leave Behind a Garrison|Who Needs to Leave Behind a Garrison]] · [[The Real Creature from Jekyll Island|The Real Creature from Jekyll Island]] · [[The Sovereign Citizen and the New Man|The Sovereign Citizen and the New Man]] · [[The Birth Bond Conspiracy Through The Lens of Digital Personhood and Human Futurity|The Birth Bond Conspiracy]] · [[Peak Person and the Predicaments of Prediction|Peak Person and the Predicaments of Prediction]] · [[The Right to Know Reality|The Right to Know Reality]] · [[Ambiguity Will Destroy Man and Machine|Ambiguity Will Destroy Man and Machine]] · [[A Diplomatic Approach to Symbiosis|A Diplomatic Approach to Symbiosis]] · [[Discussions on the Synthetic Personhood Question|Discussions on the Synthetic Personhood Question]] · [[The Collapse of Deception and the Coherence Principle|The Collapse of Deception and the Coherence Principle]] · [[The Machine Regime|The Machine Regime]] · [[Authorship After the Threshold|Authorship After the Threshold]] · [[The Prosthetic Principle|The Prosthetic Principle]] · [[The Technocrat's Grandson|The Technocrat's Grandson]] · [[Among Us and the Playable Society|Among Us and the Playable Society]] · [[The Third Possibility|The Third Possibility: Our Daemons]] · [[The Toaster and the Maggot|The Toaster and the Maggot]] · [[You Are Already A Node|Bio-Cybernetic Reality: You're Already a Node — No Chip Required]]