Researched general backup strategy (not gdrive-specific) -- 3-2-1 rule, what to prioritize backing up, database-safe-copy practices, restore testing. 3 new media.db saves (M0014-M0016). Added RULE 7 (restore verification, quarterly) to SOP-BACKUP.md -- nothing like this existed in governance before. Added 3-2-1 rationale + explicit app-data-vs-app-code scope clarification to SOP-DATA-BACKUP.md (answers open question from earlier session: app code stays on-server via BACKUP.php, app data/state goes to Drive same as system DBs). Flagged (not fixed directly, Server 40's call) that SOP-DB-BACKUP.md's bootstrap uses raw copy() on live WAL-mode SQLite DBs, which every source warns can silently corrupt -- filed T760, low priority, no observed failure yet.