---
id: TST-PFM-DJE-011
title: Commit split
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/commit-split.spec.ts
implements:
  - ATS-PFM-DJE-003-05
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/commit-split.spec.ts'
assertion_inventory:
  - committing with splitting
  - opens one transaction and commits every object when nothing fails
  - 'halves the unit until the failing object stands alone, and isolates only it'
  - 'keeps the error that isolated the object, which is what the rejection is classified from'
  - isolates a single object that fails without splitting anything
  - 'isolates every object when every one of them fails, and commits none'
  - asks nothing of the database for an empty unit
  - stays inside the transaction bound for every number of failing objects in a batch of 25
  - 'lets a systemic error through, leaving what had already committed committed'
  - bounds a set with no failures at one transaction and a set that all fails at 2n-1
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Commit split

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