---
id: ADR-PFM-DJE-014
title: Daily owner-authorized partition maintenance
product_area: platform
module: data-job-engine
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
decision: >-
  One daily migration function maintains registered monthly history partitions;
  module ownership remains provisional pending the recorded ownership question.
constrains:
  - WF-PFM-DJE-017
  - SVC-PFM-DJE-partitions
  - RESP-PFM
origin: specs/PRODUCT-AREAS.md MOD-PFM-DJE row; OQ-PFM-DJE-004 (open)
alternatives:
  - option: Partition job receipts and rejections immediately
    why_not: >-
      Current schema tooling does not express this partitioning; the cited
      proposal defers it.
  - option: Delegate each table’s maintenance to its service owner
    why_not: 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.
supersedes: []
evidence:
  - 'services-platform at ad3f6a65: modules/partitions/**; docs/partitions.md'
  - 'macroservice-libraries at 54536a44: README.md#Partitioning is deferred'
---

# 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.