FG-0706 Redundant Backup Strategy
Description
Implement multiple, independent backup mechanisms for all critical data and knowledge. In human-AI collaboration, context loss is the ever-present threat. A single backup is not a backup: it's a single point of failure. Redundant Backup Strategy ensures that critical knowledge exists in at least three independent locations, using at least two different mechanisms, with regular verification that backups are current and restorable.
Implementation
Identify all critical data (source code, knowledge repositories, governance documents, session histories). Establish three backup locations using at least two different mechanisms (e.g., git + cloud sync + local copy). Automate backup where possible. Verify backup integrity monthly. Document restoration procedures and test them quarterly.
Success Indicators
- Critical data exists in 3+ independent locations
- Backups are automated and verified regularly
- Restoration procedures are documented and tested
- The team has recovered from at least one data loss event using backups
Failure Modes
- Backups exist but have never been tested for restoration
- All backups in the same location: single point of failure
- Backups not current: restoring stale data
- Backup procedures documented but not automated: relies on human memory