---
id: TST-PFM-LLM-018
title: Database checks for Executions
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/executions.integration.spec.js
implements:
  - ATS-PFM-LLM-001-12
  - ATS-PFM-LLM-002-07
  - ATS-PFM-LLM-003-01
  - ATS-PFM-LLM-003-02
  - ATS-PFM-LLM-003-03
  - ATS-PFM-LLM-003-04
  - ATS-PFM-LLM-003-05
  - ATS-PFM-LLM-003-06
  - ATS-PFM-LLM-007-09
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/executions.integration.spec.js'
source_boundary:
  provenance: observed
  source: 'services-platform:modules/llm/tests/integration/lifecycle/executions.integration.spec.js'
---

# Database checks for Executions

## Verification Boundary

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

## What This Suite Proves

Task totals agree with request settlement. Retries retain their own usage prices. Task completion and failure retain timing. Only scoped context associates requests. Nested task execution is rejected. Unknown task definitions create no record. Task totals follow settlements. Replayed task keys do not rerun work. Refusal retains the original decision figures. 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 catalog, ledger, request or task state writes, execution context and tool loop are real. The model is scripted and captured evidence uses memory storage; task telemetry is recorded where that suite asserts it.

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