---
id: TST-PFM-SEC-239
title: Workspace purge functions 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/tenants/tests/integration/services/deletion/tenant-purge-functions.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/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#platform.purge_tenant_communications:
      one table a call, until the tenant has none left
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#leaves
      the tenant no communication row at all
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#works
      on one table a call, never on several at once
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#reports
      nothing removed only once the tenant is empty
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#leaves
      the other tenant’s communications exactly as they were
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#platform.purge_tenant_security:
      one table a call, until the tenant has none left
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#leaves
      the tenant no security row at all
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#removes
      the invitations that name a user before the users they name
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#takes
      the tenant’s former users with it: a deleted person’s name is kept for the life of the tenant
      and no longer
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#removes
      the identities and sessions that name the pool before the pool itself
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#works
      on one table a call, never on several at once
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#leaves
      the other tenant’s security exactly as it was
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#platform.purge_customer_security:
      one table a call, until the customer has none left
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#leaves
      the customer no security row of its own at all
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#takes
      the customer’s former users with it, as the tenant purge takes the tenant’s
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#removes
      the assignments that name a role before the roles they name
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#works
      on one table a call, never on several at once
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#leaves
      the other customer’s security exactly as it was
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js#never
      touches a role or a policy the product owns
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The file declares no substituted collaborators.
evidence:
  - >-
    services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-functions.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/tenants/tests/integration/services/deletion/tenant-purge-functions.integration.spec.js
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# Workspace purge functions 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 workspace purge functions.

## 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 file declares no substituted collaborators.

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