Platform maintains selected history tables in monthly partitions. The scheduled pass ensures the current month and the configured months ahead. Existing partitions remain intact. Retirement uses the table’s archive contract before removing expired storage. The helper contract governs child-table security and UTC boundaries. One table’s failure is recorded while the remaining table passes continue. A failed pass produces the failure metric rather than a success heartbeat. Separate alarms identify failures and prolonged absence of successful runs. This registered scope serves history outside job processing. Product still needs to decide its long-term module home.
Workload protection groups this scheduled storage maintenance with capacity operations.
The Formal Contract
The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
Outcomes
Registered tables have current and future monthly partitions.Expired partitions follow archive-before-drop retirement.Per-table failures are visible without stopping other table passes.
Surfaces
job
Controls
22 controls apply, from the corpus control catalogue.
6 rules, 4 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.
Id
Rule
Kind
Enforced at
Provenance
01must prove
Proposed
The daily 03:17 UTC schedule ensures the current month and next two months for registered tables, leaving existing partitions intact.
Expired partitions follow detach, archive and drop ordering; the helper contract retains detached secured data after archive failure for a later attempt.
A table failure is reported in an overall failed run while other table passes continue; failure metrics and full-run heartbeat metrics support separate alarms.