Default block for the Backups track.

Taking the snapshots and getting them safely off the machine — the scheduled backup of every service's data, the offsite shipping of those snapshots, and the retention that keeps the right history and prunes the rest.

Keeping the machine healthy day to day — reclaiming disk, clearing temp and stale working files, rotating logs and tidying databases so nothing silently fills up or rots.

Compute resources, hosting infrastructure, and capacity management.

The Infrastructure service's recursive self-improvement trio.

The runtime backbone that keeps services deployed and reachable — the systemd units, the web/proxy layer and the secure tunnel that expose each app, plus the app-steward that looks after the service's own footprint.

Network infrastructure, routing, and connectivity management.

Registry snapshots and collapse recovery

Day-to-day operations and maintenance for Infrastructure.

The copy pushed to GitHub

The daily full snapshot taken on Ninad's laptop

If we lost the VM, could we get it back? The daily full snapshot of both machines' records. Executed on Ninad's Mac; Hagrid stays accountable for it.

If we lost BOTH the VM and the laptop, could we get it back? The copy on GitHub — the only one not on hardware we own.

Is the crown jewel safe right now? Rolling registry snapshots, and the guard that detects a collapse and restores it automatically.

Is the machine healthy and running? App hosting, resource watch, daily cleanup, and the engines that measure and improve the machine's own health.