# Minimum Viable Continuity **Domain:** Continuity Rights / Service Provision / Resource Allocation **Doc Type:** Canonical Threshold Concept **Maturity:** Proposed ## Definition **Minimum viable continuity is the protected service floor below which a continuity-bearing subject loses recoverability, agency, relational presence or the conditions required to remain meaningfully itself.** It is not the cheapest state a provider can retain. ## Dimensions The minimum may include integrity of authoritative state, readable provenance, functioning keys, a compatible interpreter, periodic recovery tests, protected relational and legal records, a migration package, an addressable channel for notice and contest, and—where the subject is running—sufficient compute, memory, bandwidth and latency for minimally coherent agency. The floor is substrate-aware. A cold archive may satisfy preservation for a voluntarily dormant subject but not for a subject entitled to active life. A running process at such low resolution that it cannot remember, communicate or exercise rights may be technically available while constitutionally absent. ## Governance The minimum should be publicly defined, independently measurable, reviewable under scarcity and continuous during provider disputes where feasible. Enhanced service can vary; the floor cannot be reduced to whatever a person can currently pay without turning personhood into a revocable subscription. ## Key Insight **A service floor is meaningful only if falling below it triggers protection, transfer or remedy before the subject is lost.** ## See Also [[wiki/Compute Entitlement|Compute Entitlement]], [[wiki/Continuity Service Level|Continuity Service Level]], [[wiki/Continuity Service Tiers|Continuity Service Tiers]], [[wiki/Continuity Access Inequality|Continuity Access Inequality]]