⚙️ System Cron Jobs & Tasks

🔄 Shared Trends Architecture
All 3 posters share the same trends.json for weighted property selection. Trends re-generate every Monday at 6:00 AM.

📋 Note: Report generation jobs run via system crontab for reliability (avoiding gateway timeout issues). All 10 entries are active and run daily or weekly.

🔒 Backup architecture (updated 27 Aug 2026)
1 · Déjà Dup → TrueNAS (RAID1) — encrypted duplicity chain pushed to smb://truenas.local/a1private. This is now the primary copy, scheduled by Déjà Dup itself rather than cron, so it does not appear in the block above.
2 · NAS ⇒ USB mirror — nas-usb-rsync.sh, Tue & Sat 3:00 AM, rsyncs the NAS chain onto the OpenClaw_Backup USB drive (ext4, UUID-pinned). Four guards run before it transfers: USB UUID must match, NAS mount must be present (best-effort remount first), source must be readable and non-empty, and ≥1 GB free. That third guard matters most — --delete against a stale gvfs mount that reads as empty would otherwise erase the entire offline copy. Log: logs/nas-usb-rsync.log.
3 · MEGA — online / off-site — a further copy is kept in a MEGA cloud account. This is the only layer that survives events the other two share a room with (fire, theft, flood, ransomware on the LAN). It is managed outside this host's cron — no MEGA client is installed here — so it is intentionally absent from every table on this page.
Retired: usb-backup-run.sh (duplicity direct → USB, formerly Sunday 1:15 AM) was unscheduled 27 Aug 2026 — it wrote a second, independent encrypted chain to the same physical stick as layer 2, which added cost without adding a failure domain. The script is kept on disk for ad-hoc encrypted snapshots and for restores.
⚠ Worth remembering: layers 1 and 2 are the same duplicity chain, so a corrupt chain gets faithfully mirrored rather than caught. Periodic test restores from the NAS — not file counts — are the only real verification.