Daily Owner-Authorized Partition Maintenance

Context

Platform history tables use partitions, while data-job evidence currently does not.

Decision and Origin

One daily migration function maintains registered monthly history partitions; module ownership remains provisional pending the recorded ownership question. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

Alternative Comparison

Partition job receipts and rejections immediately: Current schema tooling does not express this partitioning; the cited proposal defers it.

Delegate each table’s maintenance to its service owner: Separate maintenance functions would each need schema-owner authority.

Consequences

Job evidence remains unpartitioned and requires its own retention mechanism.

This module currently carries maintenance for history owned elsewhere.