---
id: TST-PFM-DJE-153
title: Capacity override persistence
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: services-platform
files:
  - modules/capacity/tests/integration/services/persistence/capacity-state-pins.integration.spec.js
implements:
  - ATS-PFM-DJE-019-05
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:
  - >-
    services-platform:modules/capacity/tests/integration/services/persistence/capacity-state-pins.integration.spec.js
assertion_inventory:
  - 'capacity persistence: the capacity_state_pins writes'
  - replacing the pin twice
  - answers no previous pin for the first
  - answers the first pin as what the second replaced
  - 'keeps one row, the second pin, at version 2'
  - removing the pin
  - answers the pin it removed
  - leaves no row
  - removing when nothing is pinned
  - answers nothing removed
  - the persistence rules
  - 'refuses a state that is not one of the four, naming state'
  - 'refuses a blank reason, naming reason'
  - 'refuses an expiry that has passed, naming expires_at'
  - 'refuses an expiry more than a day ahead, naming expires_at'
  - 'refuses an expiry that is not an instant, naming expires_at'
  - leaves the stored pin unchanged after every refusal
  - the table
  - refuses a second row by its id check
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Capacity override persistence

## 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 capacity override persistence. 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 pin and audit services use real Postgres. Caller contexts, clocks and observability are supplied by the fixture.

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