---
id: TST-PFM-DJE-038
title: Version capture
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/version-capture.spec.ts
implements: []
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/version-capture.spec.ts'
assertion_inventory:
  - version capture at validation
  - 'keeps one version per item prevalidation read, keyed by the item position'
  - keeps nothing when the domain reported no versions
  - 'reads back only a whole number, so a damaged row is no version rather than a wrong one'
  - version verification at application
  - writes an item against the version its validation captured
  - lets the version an item named itself outrank the capture
  - 'names a record changed since the validation as its conflict, with both versions and no values'
  - 'names a mismatch of the version the item asked for as version_conflict, validated or not'
  - names a rollback item whose record moved since the plan changed_since
  - 'judges nothing it has no version for, on either side'
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Version capture

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