---
id: TST-PFM-SEC-159
title: Pool account removals database and service checks
kind: integration
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: Use the prepared test database and suite-owned fixture rows; retain shared seed records.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#security
      persistence: pool_account_removals
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#queuePoolAccountRemoval
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#writes
      one row holding the work and nothing else
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#says
      it queued the work, and answers the id the row carries
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#asks
      for one outstanding removal per account and action, however many times it is asked
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#keeps
      a delete and a disable of one account apart: a revoked membership that is then deleted needs
      both
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#claimPoolAccountRemovals
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#takes
      the oldest row, and exactly as many as it was asked for
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#leaves
      the other two alone, unclaimed: the limit binds, which a sublink would not have made it do
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#stamps
      the claim it took with the moment it lapses, and nothing else about it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#offers
      a held row to nobody else while the claim stands
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#offers
      it again once the claim has lapsed, so a run that died costs a minute and no work
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#deletePoolAccountRemovals
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#removes
      the rows the queue accepted and leaves the ones it refused
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js#does
      nothing at all when the queue accepted nothing
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite controls the clock at the declared seams; those collaborators remain outside its live
  proof.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  The file has no scenario binding established by this examination. Its executable checks remain
  registered without assigning them broader acceptance coverage.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/persistence/pool-account-removals.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries:
    - the clock
---
# Pool account removals database and service checks

## Verification Boundary

The file exercises database or service behavior through the local integration harness. The assertion references identify the source checks for pool account removals.

## What This Suite Proves

The file supplies executable engineering checks for the named subject. No complete acceptance scenario is inferred from the file’s existence.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite controls the clock at the declared seams; those collaborators remain outside its live proof.

## Must Not Be Doubled

Keep the queried database, applicable constraints and transaction boundaries real. Provider substitutes cannot establish delivery, cloud execution or cross-service recovery.