Single source of truth for every backup path & naming pattern
Before backing up anything:
1. Find the file below — use its exact path + pattern
2. If it's NOT here — add it before backing up
3. Run BACKUP.php with the correct path
4. Never use "current" / "previous" / "latest" in a filename — ever
5. Backup BEFORE making changes — not after
Naming Pattern — Universal
[item-name]-v[V]-[MM-DD-YY]-[HHMM].[ext]
e.g. db-admin-v2.2-07-17-26-0630.html
e.g. records-api-v1.0-07-17-26-0845.php
NEVER: current, previous, latest, new, old, backup, copy — in any filename.
Backup Groups — Bulk Commands
"backup critical infrastructure" → runs ALL CRITICAL groups in sequence. Always SNAPSHOT before CLEAN.
Registry — By File (click a category)
Per-System Governance Files (LEGACY + WHITELIST)
Each system's gov/ dir has LEGACY-[code].md + WHITELIST-[code].md. Naming: [SYSNAME]-LEGACY-[code]-v[V]-[MM-DD-YY]-[HHMM].md → backups/[NN]-[name]/governance/
Databases
DBs are binary — back up via bootstrap PHP (SOP-DB-BACKUP.md), NOT file_write_web.php. NEVER use BACKUP.php for .db files.
Snapshot Retention
Keep the 4 most recent platform_snapshot_*.zip in backups/snapshots/. Older → backups/snapshots/trash/ (never hard-deleted). Trash lifecycle: >3 days → trash/archive/, >5 more days → deleted.
Registry of Registries
BACKUP-REG.md
This page's source. Backup paths and naming for every platform file.
SOP-BACKUP.md
Backup SOP. Step-by-step procedures for every scenario.
SOP-CLEAN.md
Clean SOP. When/how to run CLEAN.php + CLEANBACKUPS.php.