---
id: TST-PFM-NOT-112
title: registry tables
kind: unit
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/notifications/tests/unit/registry-tables.spec.js
implements:
  - ATS-PFM-NOT-008-05
  - ATS-PFM-NOT-008-08
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Per-process test inputs and installed doubles.
assertion_bindings:
  - scenario: ATS-PFM-NOT-008-05
    suite: TST-PFM-NOT-112
    assertions:
      - >-
        services-platform:modules/notifications/tests/unit/registry-tables.spec.js#registers
        the instances as monthly-partitioned on created_at, thirteen months kept
        and two ahead
  - scenario: ATS-PFM-NOT-008-08
    suite: TST-PFM-NOT-112
    assertions:
      - >-
        services-platform:modules/notifications/tests/unit/registry-tables.spec.js#exempts
        exactly the catalog among the module’s tables as a tenantless registry,
        with a reason
      - >-
        services-platform:modules/notifications/tests/unit/registry-tables.spec.js#gives
        every other table a tenant_id for the policy to bind
evidence:
  - 'services-platform:modules/notifications/tests/unit/registry-tables.spec.js'
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: the table declarations and the exemption lists. Doubled: nothing.
    Never doubled: the declarations.
---

# registry tables

## Verification Boundary

This suite checks isolated calculations, validation or presentation with process-local inputs. It does not establish a deployed workflow.

## What This Suite Proves

Its cases exercise 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 test file identifies its pure inputs or presentation doubles. Console component suites use recorded request handlers; pure validation suites require no external provider.

## Must Not Be Doubled

The calculation, validator or component under test must execute its real implementation. Doubles supply inputs and external responses without replacing the behavior being proved.