---
id: TST-PFM-NOT-102
title: submit notification request
kind: integration
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/notifications/tests/integration/services/requests/submit-notification-request.integration.spec.js
implements:
  - ATS-PFM-NOT-002-03
  - ATS-PFM-NOT-002-05
  - ATS-PFM-NOT-002-07
  - ATS-PFM-NOT-010-03
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-002-03
    suite: TST-PFM-NOT-102
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/requests/submit-notification-request.integration.spec.js#answers
        the same request id and a duplicate for a repeat, writing one row
  - scenario: ATS-PFM-NOT-002-05
    suite: TST-PFM-NOT-102
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/requests/submit-notification-request.integration.spec.js#refuses
        a malformed envelope naming each path, with nothing written and nobody
        nudged
      - >-
        services-platform:modules/notifications/tests/integration/services/requests/submit-notification-request.integration.spec.js#refuses
        an audience reason of more than 200 characters or with a line break,
        with nothing written
  - scenario: ATS-PFM-NOT-002-07
    suite: TST-PFM-NOT-102
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/requests/submit-notification-request.integration.spec.js#is
        not found for an id Platform knows nothing of
  - scenario: ATS-PFM-NOT-010-03
    suite: TST-PFM-NOT-102
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/requests/submit-notification-request.integration.spec.js#accepts
        an audience reason and carries it to the words of the rule
evidence:
  - >-
    services-platform:modules/notifications/tests/integration/services/requests/submit-notification-request.integration.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: PostgreSQL with row-level security on, the real library insert, the
    real orchestrator behind it. Doubled: the dispatcher
  - >-
    nudge (a recorder). Never doubled: the database, the library or the
    services.
---

# submit notification request

## 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 deduplicate publication receipts; reject invalid envelopes before insertion; require a known cancellation target and reason; prefer the producer's supplied explanation.

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 notification fixtures use real PostgreSQL and module logic. Queue publication, visibility changes, nudges and installed channel adapters are recorded at their seams when the suite needs them. 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.