Little7 BC/DR

Create, maintain, and verify Little7 business continuity and disaster recovery backups for identity, memory, learnings, scripts, and local skills. Use when setting up daily/weekly backups, pruning retention, preparing Google Drive continuity archives, testing restore readiness, or updating the Little7 BC/DR file set and backup workflow.

Use this skill to preserve Little7 continuity with low-drama, repeatable backups.

Core workflow

1. Review the included README.md for scope and retention.
2. Use scripts/little7_backup.sh daily for daily snapshots.
3. Use scripts/little7_backup.sh weekly for weekly snapshots.
4. Verify the archive exists and contains the expected files before claiming success.
5. Prefer short, factual status updates: what was backed up, where it went, and what was pruned.

Backup targets

Default inclusion is defined inside scripts/little7_backup.sh.

The intent is to preserve:

• core identity files
• curated memory
• learnings
• local scripts
• local skills
• selected ledgers/docs

The intent is to exclude:

• secrets unless explicitly allowlisted
• tokens
• browser profiles
• caches
• dependency trees
• disposable temp artifacts

Destination model

Primary destination defaults to Google Drive, with this folder structure:

• Little7/daily/
• Little7/weekly/
• Little7/latest/
• Little7/restore-notes/

Do not silently assume the exact local mount path; check environment variables or configured sync location first.

Retention

• Daily: keep 180 copies
• Weekly: keep 312 copies

Prune oldest matching archives only after a new archive is successfully created.

Restore discipline

When asked to verify BC/DR readiness, do not just inspect archive names. At minimum:

1. list archive contents
2. confirm critical files are present
3. report any missing identity/memory files clearly

Resources

• Public usage notes: README.md
• Backup implementation: scripts/little7_backup.sh