---
id: TST-PFM-NOT-033
title: dispatch communications
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/dispatch/dispatch-communications.integration.spec.js
implements:
  - ATS-PFM-NOT-018-01
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-018-01
    suite: TST-PFM-NOT-033
    assertions:
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/dispatch-communications.integration.spec.js#publishes
        every row of the tenant it was given, oldest first
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/dispatch-communications.integration.spec.js#publishes
        a pointer and nothing of the request: the version, the kind, the tenant
        and the key
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/dispatch-communications.integration.spec.js#leaves
        the refused row and deletes the accepted one
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/dispatch-communications.integration.spec.js#offers
        it again once its claim has lapsed, and nothing on the row says it was
        ever refused
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/dispatch-communications.integration.spec.js#finds
        nothing for the second run, because the first run holds the claim
      - >-
        services-platform:modules/communications/tests/integration/services/dispatch/dispatch-communications.integration.spec.js#stops
        before it enters a tenant, so the run ends inside the function’s timeout
evidence:
  - >-
    services-platform:modules/communications/tests/integration/services/dispatch/dispatch-communications.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),
    the claim, the delete and the dispatcher.
  - >-
    Doubled: the send queue (recorded, with scripted refusals). Never doubled:
    the database, its constraints, the claim or the
---

# dispatch communications

## 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 dispatch committed pointers with recoverable 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.