tegwick e7aa485c9f Complete DISCTL-WP-0002-T01: Forgejo off-Gitea mirror

Create private coulomb/disaster-control on forgejo.coulomb.social,
add mirror sync docs and tools/sync-mirror.sh, update registers and
README. Mark T01 done.

2026-07-07 20:28:58 +02:00

1.6 KiB

Raw Permalink Blame History

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.

Role	Location	Refresh	Status
Primary	`gitea.coulomb.social/coulomb/disaster-control`	`git push origin`	operational
Mirror	`forgejo.coulomb.social/coulomb/disaster-control` (private)	`./tools/sync-mirror.sh` after push to origin	operational

Forgejo runs on railiance01 — independent of CoulombCore/Gitea. See docs/mirror-sync.md for setup and recovery.

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