# Continuity Service Tiers
**Entity class:** Concept or analytic term
**Domain:** Continuity Infrastructure / Preservation / Execution
**Doc Type:** Canonical Operational Taxonomy
**Maturity:** Proposed
## Definition
**Continuity service tiers distinguish preservation from readiness and active execution without treating every stored state as a running person.** The tier describes an operational condition, not the moral rank of the subject.
## Canonical Tiers
- **Cold continuity:** protected state, provenance, keys and interpreters are preserved for future verification or restoration, but no subject is assumed to be executing.
- **Warm continuity:** state remains periodically validated, migration-ready and recoverable within a defined interval; limited services may maintain identity, notice and relational records.
- **Hot continuity:** an executable continuant is actively scheduled with a declared compute, memory, latency, bandwidth and recovery envelope.
Transition among tiers requires authority and disclosure. Moving a running subject to cold storage is suspension, not ordinary archival housekeeping. Activating an archive can instantiate a new process whose identity and standing require separate assessment. Restoring a warm or cold state must disclose the chosen state and missing interval under [[wiki/Restoration Disclosure|Restoration Disclosure]].
Technical tiers are not [[wiki/Continuity Service Class|Continuity Service Classes]]. A service class is a legal-administrative bundle of entitlements; a tier is an operational state. An archive-only election may authorize cold preservation but no activation, while an active-continuation class may entitle a recognized subject to hot service under a measurable service level.
## Key Insight
**Storage preserves the possibility of execution; it does not prove that a subject is present.**
## See Also
[[wiki/Hot Interpreter and Cold Archive|Hot Interpreter and Cold Archive]], [[wiki/Long-Term Digital Preservation|Long-Term Digital Preservation]], [[wiki/Minimum Viable Continuity|Minimum Viable Continuity]], [[wiki/Operational Continuity|Operational Continuity]]
<!-- BEGIN DEEP TIME CONTINUITY INTERFACE -->
## 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.
<!-- END DEEP TIME CONTINUITY INTERFACE -->
## 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]], [[articles/The Architecture of Continuity and Emerging Neuroinformatics Standards|The Architecture of Continuity and Emerging Neuroinformatics Standards]], 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
- **Continuity Service Tiers** is associated with cold continuity.
- **Continuity Service Tiers** is associated with warm continuity.
- **Continuity Service Tiers** is associated with hot continuity.
### Connections in this corpus
- [[wiki/AI Factory|AI Factory]] is connected in the corpus with **Continuity Service Tiers**. Cold/warm/hot service tiers map onto different compute/storage commitments.
- [[wiki/CoreWeave|CoreWeave]] is connected in the corpus with **Continuity Service Tiers**. Inference capacity can operationalize differential activation/latency tiers.
### Technology and research relationships
- [[wiki/S-LoRA|S-LoRA]] converges technically with **Continuity Service Tiers**.
<!-- END HUMANIZED RELATIONSHIPS 2026-09-11 -->
## Read First in the Wiki
<!-- BEGIN HUMANIZED WIKI ROUTES 2026-09-11 -->
- [[wiki/Continuity Access Inequality|Continuity Access Inequality]] — supplies the related concept or analytic term context needed to place **Continuity Service Tiers** within the wider system.
- [[wiki/Hot Interpreter and Cold Archive|Hot Interpreter and Cold Archive]] — supplies the related concept or analytic term context needed to place **Continuity Service Tiers** within the wider system.
- [[wiki/Long-Term Digital Preservation|Long-Term Digital Preservation]] — supplies the related concept or analytic term context needed to place **Continuity Service Tiers** within the wider system.
- [[wiki/Minimum Viable Continuity|Minimum Viable Continuity]] — supplies the related concept or analytic term context needed to place **Continuity Service Tiers** within the wider system.
- [[wiki/Restoration Disclosure|Restoration Disclosure]] — supplies the related concept or analytic term context needed to place **Continuity Service Tiers** within the wider system.
<!-- END HUMANIZED WIKI ROUTES 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]], **Host-infrastructure crosswalk** provides the narrative context for **Continuity Service Tiers**: The remaining cross-links make the boundary conditions explicit.
<!-- END HUMANIZED CORPUS ROUTES 2026-09-11 -->
## Research Edges
<!-- 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
This entry is expanded through the concrete host-side relationships and status-qualified edges below.
#### Outgoing typed edges
- **HR-0052 — `classifies` → `cold continuity`** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki.
- **HR-0053 — `classifies` → `warm continuity`** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki.
- **HR-0054 — `classifies` → `hot continuity`** — **CORPUS ARCHITECTURE**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Core host/residual architecture from article and continuity wiki.
- **HR-0513 — `wiki_links_to` → [[wiki/Hot Interpreter and Cold Archive|Hot Interpreter and Cold Archive]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Continuity Service Tiers.md`.
- **HR-0514 — `wiki_links_to` → [[wiki/Long-Term Digital Preservation|Long-Term Digital Preservation]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Continuity Service Tiers.md`.
- **HR-0515 — `wiki_links_to` → [[wiki/Minimum Viable Continuity|Minimum Viable Continuity]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Continuity Service Tiers.md`.
- **HR-0516 — `wiki_links_to` → [[wiki/Restoration Disclosure|Restoration Disclosure]]** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Continuity Service Tiers.md`.
#### Incoming typed edges
- **HR-0389 — [[wiki/Continuity Access Inequality|Continuity Access Inequality]] `wiki_links_to` → this entry** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Continuity Access Inequality.md`.
- **HR-0738 — [[wiki/Long-Term Digital Preservation|Long-Term Digital Preservation]] `wiki_links_to` → this entry** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Long-Term Digital Preservation.md`.
- **HR-0790 — [[wiki/Minimum Viable Continuity|Minimum Viable Continuity]] `wiki_links_to` → this entry** — **EXISTING WIKI EDGE**; evidence `WIKI_ARCHIVE`. Direct internal link currently present in `Minimum Viable Continuity.md`.
- **HR-1377 — [[wiki/AI Factory|AI Factory]] `cross_threads` → this entry** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Cold/warm/hot service tiers map onto different compute/storage commitments.
- **HR-1387 — [[wiki/CoreWeave|CoreWeave]] `cross_threads` → this entry** — **HIGH VALUE CROSS THREAD**; evidence `ARTICLE`, `WIKI_ARCHIVE`. Inference capacity can operationalize differential activation/latency tiers.
- **HR-1580 — [[wiki/S-LoRA|S-LoRA]] `technical_convergence_with` → this entry** — **ARCHITECTURAL ANALOGY**; evidence `WEB_SLORA`, `WIKI_ARCHIVE`. Cheap dormant specialization + active GPU residency is a useful resource-allocation analogue, not evidence of digital persons.
<!-- END HOST RESIDUAL RELATIONSHIP GRAPH 2026-09-10 -->