---
id: TST-PFM-SEC-043
title: Customers.table 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/customers/tests/integration/db/customers.table.integration.spec.js
implements:
  - ATS-PFM-SEC-001-03
  - ATS-PFM-SEC-001-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: Use the prepared test database and suite-owned fixture rows; retain shared seed records.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#customers
      table: the constraints the database enforces
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      a type outside the closed list by customers_type_check
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      a sys_locked value outside the closed list by customers_sys_locked_check
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      a second row with the same id by the customers_pk primary key
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#stores
      a canonical address written directly, the negative control for the domain’s checks
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      an address with an uppercase letter by the domain’s email_address_canonical_check
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#stores
      an address with surrounding whitespace trimmed, because the trigger removes it before the
      domain sees it
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      an address with whitespace inside it by the domain’s email_address_canonical_check
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#stores
      no address at all when given an empty one, because an empty string is never a stored value
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      a value that is not shaped like an address by the domain’s email_address_format_check
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      an address whose domain has no dot by the domain’s email_address_format_check
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      a row with no type, naming the column
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      a row with no creator, naming the column
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#holds
      none of the three columns migration 0078 dropped, so nothing can write a balance or a security
      flag
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#still
      holds the columns the record is made of, the premise of the absence above
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#refuses
      deleting a customer that tenants still reference by tenants_customer_fk
  - provenance: test
    source: >-
      services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js#leaves
      the referenced customer in place after the foreign key refuses the delete
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The file declares no substituted collaborators.
evidence:
  - 'services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js'
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: 'services-platform:modules/customers/tests/integration/db/customers.table.integration.spec.js'
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# Customers.table 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 customers.table.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

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