Every deposited ZIP carries a compliance-mode object lock with 7-year retention (DESIGN.md D22) — platform-immutable, not even the account owner can delete early. Retention is a period, not "forever": the archive's permanence promise (RFC §2.2) therefore needs an extension practice.
To decide and document:
- extension cadence (e.g. re-lock everything to a fresh 7 years every N years — extending is always allowed, shortening never is);
- where that runs (a scheduled workflow re-applying retention is cheap);
- what the mirror guidance says about archival copies as the second line.
Nothing is at risk before 2033; deciding early is the point.
Every deposited ZIP carries a compliance-mode object lock with 7-year retention (DESIGN.md D22) — platform-immutable, not even the account owner can delete early. Retention is a period, not "forever": the archive's permanence promise (RFC §2.2) therefore needs an extension practice.
To decide and document:
Nothing is at risk before 2033; deciding early is the point.