Lifeboat

Default box-files coverage is Complete: include every file regardless of size or type, including old backups and installers; the only exclusions are passwords/keys/secrets, Lifeboat's own backup output, version-control folders, and caches that rebuild themselves.

Before each nightly build, review any new file left out only because its name looks like a secret: include it if it is ordinary code, docs, a screenshot or data with no visible credential; keep out credential stores, plain-text logins, one-time-code logs and anything uncertain; record the counts in the run log.

Never rewrite a backup file in place; upload a new version, verify it, then move the superseded file to trash (many storage services keep old versions that count against quota).

Use for Lifeboat's first conversation with a new owner: orientation, storage setup, first verified backup.

Use on Lifeboat's first day, or when its tools are missing or failing, to build and test the backup programs before the first real backup.

Use when setting up Lifeboat for a new user: choose where backups go, scope, schedule, coverage, first run and after-run items.

Use for every scheduled or first Lifeboat backup: the daily box-files copy, the weekly bot pack, and opted-in repositories, each verified before any older copy is retired.

Use before every Lifeboat upload to ensure no password, token, key, login or card number is stored.

Use after a verified Lifeboat backup to retire older copies inside the Lifeboat folder according to the chosen retention mode, and to send the trash reminder when the trashed amount reaches the configured limit.

Use monthly to prove a Lifeboat backup can be restored, then create the monthly copy.

Use when the user needs to bring bots or box files back from a Lifeboat backup.

Use when a Lifeboat run fails or is missed, storage is low, or a check needs a retry; includes the daily missed-run check.

Use only after the user agrees, to measure backup accuracy against one bot.