`disaster-control` is the **Resilience Control Plane** for Coulomb Social / Helix Forge and adjacent endeavors. It is the single source of truth for recovery — independent of any one server — answering: what exists, what must survive, how it is rebuilt, and whether restore actually works.
The framing is **business continuity + disaster recovery + cyber recovery + evidence**, informed by ISO 22301, NIST CSF 2.0, NIST SP 800-34, and CISA backup guidance.
## What lives here
- **Registers** — `AssetRegister.yaml`, `DataRegister.yaml`, service dependency map
- **Test evidence** — dated restore-drill reports proving RTO/RPO are actually met
## Operating principle
> Every capability that becomes valuable must declare its source of truth, recovery method, backup schedule, RTO, RPO, owner, and restore test evidence.
Servers are disposable; data, identity, secrets, evidence, and payment/account records are not. Rebuild (Ansible/IaC + data restore + secret recovery + DNS cutover) is the default recovery pattern, not server resurrection.
## Boundaries
This repo documents, plans, and evidences resilience for the Coulomb stack. It does not host application runtime code, and it does not own the backup tooling itself (restic, Velero, `gitea dump`, etc. run where the infrastructure lives). Extracting the control plane into a standalone product is explicitly deferred.
