---
id: TST-PFM-DJE-015
title: Define data operation
kind: unit
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/define-data-operation.spec.ts
implements:
  - ATS-PFM-DJE-002-05
  - ATS-PFM-DJE-018-01
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: In-memory fixtures and restored dependency doubles.
evidence:
  - 'macroservice-libraries:packages/data-jobs/src/define-data-operation.spec.ts'
assertion_inventory:
  - adding a batch's impact to the job's
  - 'adds the counts, which is what makes a digest speak for every batch and not the last one'
  - 'adds a cascade count per child collection, keeping the ones only one batch reached'
  - 'adds the blocked records per reason code the domain gave, the same way'
  - takes the first batch as it stands when there is nothing yet to add it to
  - >-
    keeps what the latest batch said of anything that is not a count, rather than inventing an
    addition for it
  - declaring how an operation is rolled back
  - 'keeps the declaration, which is what the planner asks the domain through'
  - >-
    leaves an operation that declares none without one, which is how it says its jobs cannot be
    reversed
  - 'refuses a delete that declares one, because a hard delete has no undo to promise'
  - >-
    refuses a compensating operation that is not an operation kind, and a contract version that is
    not one
  - declaring what an operation prepares outside its transaction
  - 'keeps a prepare, which is what the batch runner calls before the batch transaction'
  - 'refuses a prepare that is not a function, so the mistake is a service that will not start'
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Define data operation

## Verification Boundary

The suite checks an isolated production calculation, declaration or adapter. The structured assertion inventory records the checks present at the pinned revision.

## What This Suite Proves

The existing checks exercise define data operation. The specification bindings identify the narrower outcomes supported by those assertions.

## What It Does Not Prove

An isolated check does not establish a deployed workflow, database enforcement or complete feature acceptance.

## Real Dependencies and Test Doubles

The production function or declaration is exercised with in-memory inputs and dependency doubles. This boundary does not require a live database.

## Must Not Be Doubled

The production function under examination and its returned decisions remain real; replacing their answers defeats the check.