Retention (§6.18)

archive: stale or never run

E-M7-03 production rollout of the §6.18 retention policy. Full granularity for 365d, weekly collapse 365–1825d, monthly > 1825d. Each cron run optionally archives the snapshot to R2 for disaster recovery (acceptance: lekanb@gmail.com's historical snapshots survive a Postgres restore from R2).

Status

Trigger run

Run history

(no retention runs yet)

Subject archive integrity

§6.18 acceptance: pass ?subjectRole=Founder&subjectEntityId=<uuid>.

(no subject specified)