---
id: TST-PFM-DJE-029
title: Keyed data jobs
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/keyed-data-jobs.integration.spec.ts
implements:
  - ATS-PFM-DJE-004-04
  - ATS-PFM-DJE-006-06
  - ATS-PFM-DJE-012-02
  - ATS-PFM-DJE-012-03
  - ATS-PFM-DJE-012-04
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/keyed-data-jobs.integration.spec.ts
assertion_inventory:
  - the ID crosswalk against Postgres
  - a key delivered again
  - 'creates the record and writes one crosswalk row, then updates that record and still has one row'
  - 'skips a delivery of a revision already applied, which is what a rerun of yesterday’s file is'
  - 'skips a delivery a newer one has overtaken, so a late file never undoes the current record'
  - >-
    writes no crosswalk row for an item it refused, so the corrected delivery of that key is a
    create
  - the conflict policy (§6.9)
  - refuses the delivery as a conflict and leaves the record alone
  - applies the delivery over the change when the job was submitted to overwrite
  - a child whose parent has not arrived (§6.8)
  - 'blocks the child, and a retry after the parent is loaded applies it and finishes the job'
  - >-
    refuses to retry a job whose refusals are not blocked items, because correcting records is a new
    job
  - applying a validated upsert
  - >-
    refuses an apply with no digest or a stale one, writes nothing, and applies the one that echoes
    its digest
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Keyed data jobs

## 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 keyed data jobs. 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.