---
id: TST-PFM-LLM-019
title: Database checks for AI Ledger Concurrency
kind: integration
product_area: platform
module: llm
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/llm/tests/integration/lifecycle/llm-ledger-concurrency.integration.spec.js
implements:
  - ATS-PFM-LLM-007-02
  - ATS-PFM-LLM-007-04
  - ATS-PFM-LLM-007-05
  - ATS-PFM-LLM-007-07
  - ATS-PFM-LLM-007-16
  - ATS-PFM-LLM-007-17
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/lifecycle/llm-ledger-concurrency.integration.spec.js'
source_boundary:
  provenance: observed
  source: 'services-platform:modules/llm/tests/integration/lifecycle/llm-ledger-concurrency.integration.spec.js'
---

# Database checks for AI Ledger Concurrency

## Verification Boundary

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

## What This Suite Proves

Concurrent requests share capacity atomically. Concurrency slots return on settlement. Grant windows and revocation apply at request time. Lower limits preserve running reservations. Lowering limits preserves admitted work. Grant boundaries change the next admission. 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, the production ledger, grant services, execution context and transactions are real. A controlled clock supplies boundaries; actual competing statements establish the race.

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