Replace repo-seed template identity with disaster-control across AGENTS.md, SCOPE.md, and .claude/rules. Archive REPO-WP template workplans. Document dev workflow and classification. Mark WP-0001 finished.
1.2 KiB
1.2 KiB
SCOPE
Lightweight boundary for agents and contributors.
One-liner
Resilience Control Plane for Coulomb Social / Helix Forge — recovery governance, evidence, and registers.
Core Idea
disaster-control is the single source of truth for business continuity, disaster
recovery, cyber recovery, and restore-test evidence. It documents what exists,
what must survive, how it is rebuilt, and whether restore actually works.
In Scope
- Asset and data registers (
AssetRegister.yaml,DataRegister.yaml) - Resilience and backup policy (
ResiliencePolicy.md,BackupPolicy.md,RTO-RPO-Matrix.md) - Restore runbooks and incident playbooks
- Test evidence from restore drills (
TestEvidence/) - Cross-repo backup pickup tracking (
BackupPickupQueue.md) - Panic sheet and operator recovery documentation
- State Hub workplans (ADR-001) for resilience work
Out of Scope
- Application runtime code
- Backup script implementation (lives in
railiance-cluster,railiance-platform,railiance-infra) - Owning infrastructure remediation — this repo tracks and evidences; owner repos implement
registry/capability publish (inherited template scaffold; canonical template isrepo-seed)