---
id: TST-PFM-DJE-034
title: Submission purge
kind: integration
product_area: platform
module: data-job-engine
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: macroservice-libraries
files:
  - packages/data-jobs/src/tests/integration/submission-purge.integration.spec.ts
implements:
  - ATS-PFM-DJE-005-06
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Suite-owned fixture records, job identifiers and workspace contexts; teardown removes the fixture
  data.
evidence:
  - >-
    macroservice-libraries:packages/data-jobs/src/tests/integration/submission-purge.integration.spec.ts
assertion_inventory:
  - the submission ledger is purged after its retention
  - >-
    deletes the tenant's rows older than 30 days and keeps the rest, the row exactly 30 days old
    included
  - 'leaves another tenant''s rows alone, however old'
  - 'is idempotent: a second run finds nothing to delete'
  - 'deletes in slices, oldest first, stops at its limit and lets the next run carry on'
  - 'frees the key: after the purge it no longer answers the old job'
  - takes the retention the caller gives
  - 'refuses to run in no tenant, rather than purge every tenant or none silently'
  - 'needs the DELETE grant the security SQL gives the application role, and is refused without it'
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Submission purge

## Verification Boundary

The suite checks the production service or shared engine against its database fixture. The structured assertion inventory records the checks present at the pinned revision.

## What This Suite Proves

The existing checks exercise submission purge. The specification bindings identify the narrower outcomes supported by those assertions.

## What It Does Not Prove

Local execution does not establish deployed queue, storage or service behavior. Independent test cases do not establish a complete cross-feature process.

## Real Dependencies and Test Doubles

The shared engine uses real Postgres with a test domain operation and repository. File suites use a fake object store; transport publication uses test ports.

## Must Not Be Doubled

The database effects, security context and production operation under examination remain real. Their outcomes cannot be replaced with canned success responses.