Celilo already knows how to produce a backup — a self-describing, encrypted envelope that captures everything needed to rebuild a system. Scheduled backups close the obvious gap: you shouldn’t have to remember to run one. The backup you never took is the one you needed.
Backups on a schedule
The goal is simple to state: backups that happen on their own, on a cadence you set, without an operator sitting at a terminal. A backup is only insurance if it runs before the failure, and a manual step is a step that eventually gets skipped. Automating it turns “I hope we have a recent backup” into “we always do.”
Built on the event system
Celilo already has an event-scheduling system that runs work on a cadence. Scheduled backups are meant to lean on that existing machinery rather than introduce a second, parallel scheduler — a backup is just another scheduled action the event system fires. This keeps one place responsible for “things that happen on a timer” and lets scheduled backups inherit whatever that system already does well.