---
id: TST-PFM-NOT-048
title: sender identities
kind: integration
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/communications/tests/integration/services/persistence/sender-identities.integration.spec.js
implements:
  - ATS-PFM-NOT-020-08
  - ATS-PFM-NOT-020-10
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-048
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/persistence/sender-identities.integration.spec.js#refuses
        the domain strategy with no domain to prove
      - >-
        services-platform:modules/communications/tests/integration/services/persistence/sender-identities.integration.spec.js#refuses
        a domain given to the address strategy, which proves the address alone
      - >-
        services-platform:modules/communications/tests/integration/services/persistence/sender-identities.integration.spec.js#refuses
        an address outside the domain the strategy proves, naming the domain
  - scenario: ATS-PFM-NOT-020-10
    suite: TST-PFM-NOT-048
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/persistence/sender-identities.integration.spec.js#records
        when the association’s own sender started working, the first time it is
        verified
      - >-
        services-platform:modules/communications/tests/integration/services/persistence/sender-identities.integration.spec.js#never
        clears that instant when a later reading is no longer verified
evidence:
  - >-
    services-platform:modules/communications/tests/integration/services/persistence/sender-identities.integration.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: PostgreSQL (the prepared integration database, row-level security on)
    and the sender-identity persistence service.
  - >-
    Doubled: nothing — SES is not reached from here at all; these are statements
    and rules. Never doubled: the database, its
---

# sender identities

## 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; preserve first verification through later provider states.

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.