Expand AssetRegister and DataRegister with T0/T4 stack assets. Add ResiliencePolicy, PanicSheet, full-server-loss runbook, and five incident playbooks. Update README with mirror status. Mark T02-T05, T07-T08 done; T01 and T06 in progress.
1.7 KiB
1.7 KiB
disaster-control
Resilience Control Plane for Coulomb Social / Helix Forge — the single source of truth for business continuity, disaster recovery, cyber recovery, and restore test evidence.
Purpose
Know what exists, what must survive, how it is rebuilt, and whether restore
actually works. See INTENT.md and ResiliencePolicy.md.
Key artifacts
| Path | Purpose |
|---|---|
AssetRegister.yaml |
Infrastructure and backup stream inventory |
DataRegister.yaml |
Data classes and recovery mapping |
ResiliencePolicy.md |
Operating principle, tiers, drill cadence |
BackupPolicy.md |
Backup architecture and monitoring |
RTO-RPO-Matrix.md |
Per-system recovery targets |
BackupPickupQueue.md |
Cross-repo backup implementation tracker |
PanicSheet.md |
One-page emergency reference |
RestoreRunbooks/ |
Recovery procedures |
IncidentPlaybooks/ |
Incident response steps |
TestEvidence/ |
Dated restore drill reports |
Off-site mirror (R10)
This repo must survive loss of the primary Gitea. Mirror status:
| Mirror | Location | Refresh | Status |
|---|---|---|---|
| Primary | gitea.coulomb.social/coulomb/disaster-control |
git push on commit | operational |
| Off-Gitea mirror | Not configured | — | open (DISCTL-WP-0002-T01) |
Target: at least one private mirror on infrastructure independent of
CoulombCore/Gitea (e.g. GitHub private mirror). When configured, update this
table with URL and refresh method (git push --mirror or scheduled sync).
Session orientation
cat .custodian-brief.md
cat INTENT.md
ls workplans/
State Hub sync after workplan edits:
cd ~/state-hub && make fix-consistency REPO=disaster-control