---
id: TST-PFM-LLM-027
title: Database checks for Workspace Participant
kind: integration
product_area: platform
module: llm
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/llm/tests/integration/services/maintenance/tenant-participant.integration.spec.js
implements:
  - ATS-PFM-LLM-004-04
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: Prepared local test database with suite-owned records and scoped cleanup.
evidence:
  - provenance: test
    source: >-
      services-platform:modules/llm/tests/integration/services/maintenance/tenant-participant.integration.spec.js
source_boundary:
  provenance: observed
  source: >-
    services-platform:modules/llm/tests/integration/services/maintenance/tenant-participant.integration.spec.js
---

# Database checks for Workspace Participant

## Verification Boundary

The suite checks module persistence or service behavior against prepared PostgreSQL with scoped records.

## What This Suite Proves

Organization deletion preserves its neighbors. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

## What It Does Not Prove

The suite does not establish browser behavior, deployed routing, live model quality or actual recipient inbox delivery.

## Real Dependencies and Test Doubles

PostgreSQL, production participant batching and prefix deletion are real. A memory object store models versions, pages and deletion markers through the evidence-store seam.

## Must Not Be Doubled

Retain PostgreSQL constraints, transaction behavior and the production persistence or dispatcher path under test. A scripted provider must not replace accounting or authorization.