Every infrastructure change starts with a written plan: what, where, why,
rollback. Plans land in commits or wiki edits before the change is executed.
docker compose down --volumes without explicit confirmation.git reset --hard without explicit confirmation.Replaced or decommissioned configs go to the Archive. Do not
silently overwrite. Keep enough state to roll back.
For services with their own data layer:
pg_dump, MariaDB mariadb-dump, AD ntdsutil)The BookStack -> Wiki.js cutover (2026-04-29) followed this:
/opt/wiki-bookstack-archive/mariadb-data-snapshot/opt/wiki/