---
id: TST-PFM-LLM-028
title: Database checks for Threshold Notice
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/notices/threshold-notice.integration.spec.js
implements:
  - ATS-PFM-LLM-008-03
  - ATS-PFM-LLM-008-04
  - ATS-PFM-LLM-008-05
  - ATS-PFM-LLM-008-06
  - ATS-PFM-LLM-008-07
  - ATS-PFM-LLM-008-08
  - ATS-PFM-LLM-008-10
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/notices/threshold-notice.integration.spec.js'
source_boundary:
  provenance: observed
  source: 'services-platform:modules/llm/tests/integration/services/notices/threshold-notice.integration.spec.js'
---

# Database checks for Threshold Notice

## Verification Boundary

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

## What This Suite Proves

Only active local administrators receive notices. Warning and pause messages use customer figures. Competing senders claim one delivery. Enclosing transactions defer notice delivery. Persistent delivery failure stops after three attempts. No-recipient warnings do not retry forever. Recovery retries committed owed notices. 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, crossing leases, production settlement, recipient resolution and real Administrator role assignments are real. The model, evidence bucket and email transport are scripted or recording doubles; no recipient inbox is contacted.

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