---
id: TST-PFM-NOT-070
title: notification instances table
kind: integration
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/notifications/tests/integration/db/notification-instances.table.integration.spec.js
implements:
  - ATS-PFM-NOT-005-07
  - ATS-PFM-NOT-008-05
  - ATS-PFM-NOT-008-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-005-07
    suite: TST-PFM-NOT-070
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/db/notification-instances.table.integration.spec.js#holds
        one key per tenant across months: the key table conflicts on the same
        key in two months
  - scenario: ATS-PFM-NOT-008-05
    suite: TST-PFM-NOT-070
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/db/notification-instances.table.integration.spec.js#refuses
        a row of a month with no partition rather than absorbing it in a default
        partition
  - scenario: ATS-PFM-NOT-008-08
    suite: TST-PFM-NOT-070
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/db/notification-instances.table.integration.spec.js#shows
        a tenant its own instances and not another’s, through the parent
      - >-
        services-platform:modules/notifications/tests/integration/db/notification-instances.table.integration.spec.js#shows
        no instances at all to a statement that names no tenant
evidence:
  - >-
    services-platform:modules/notifications/tests/integration/db/notification-instances.table.integration.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: PostgreSQL, the migration's partitioning, indexes and policy, the
    partition maintenance's partitions. Doubled: nothing.
  - 'Never doubled: the database, the partitions or the policy.'
---

# notification instances 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 deduplicate occurrence notices; apply retention and partition boundaries; enforce notification row visibility.

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.