---
id: TST-PFM-NOT-029
title: communication sender identities table
kind: integration
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/communications/tests/integration/db/communication-sender-identities.table.integration.spec.js
implements:
  - ATS-PFM-NOT-020-08
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Suite-owned records in the prepared integration workspaces; seeded workspace
  identities remain shared fixtures.
assertion_bindings:
  - scenario: ATS-PFM-NOT-020-08
    suite: TST-PFM-NOT-029
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/db/communication-sender-identities.table.integration.spec.js#refuses
        a second sender identity for the same tenant, by the unique rule’s name
      - >-
        services-platform:modules/communications/tests/integration/db/communication-sender-identities.table.integration.spec.js#refuses
        an address at a subdomain of it, which SES does not cover either
      - >-
        services-platform:modules/communications/tests/integration/db/communication-sender-identities.table.integration.spec.js#refuses
        a verified setting that says nothing about when it was verified
evidence:
  - >-
    services-platform:modules/communications/tests/integration/db/communication-sender-identities.table.integration.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: PostgreSQL, the migration's checks, its unique rule, its foreign key,
    its text-normalization trigger and the
  - >-
    `platform.email_address` domain. Doubled: nothing. Never doubled: the
    database or any of its rules — every statement here
---

# communication sender identities table

## Verification Boundary

This suite exercises the local services and prepared PostgreSQL database. API lifecycle cases use signed test contexts through the real route handler; they do not invoke the deployed gateway.

## What This Suite Proves

Its cases exercise validate sender strategy and domain claims.

The registered scenario bindings identify the assertions this executable file contributes. They retain individual test references so that a composite scenario does not become a claim of complete execution by one file.

## What It Does Not Prove

Local outcomes do not prove deployed queues, external provider acceptance, production credentials or complete browser behavior. No fresh execution or conformance result is claimed.

## Real Dependencies and Test Doubles

The communication fixtures use real PostgreSQL and module logic. Shared support records queue and transport calls and stores objects in memory; sender provisioning substitutes a provider identity store. Signed API contexts replace the authorizer key in API suites.

## Must Not Be Doubled

Database constraints, workspace policy, state guards and the service operation under test must remain real. Recording a provider or queue call must not replace the submission, claim or outcome logic being checked.