---
id: TST-PFM-ELG-491
title: Responsibility responsibilities notifications checks
kind: api-lifecycle
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/responsibilities/tests/e2e/responsibilities-notifications.e2e.spec.js
implements:
  - ATS-PFM-ELG-013-12
  - ATS-PFM-ELG-014-07
environment: local
implementation_state: implemented
latest_result: not-run
conformance: not-verified
estimated_minutes: 5
isolation: Prepared local test database with suite-owned fixture keys and cleanup.
evidence:
  - provenance: test
    source: >-
      services-platform:modules/responsibilities/tests/e2e/responsibilities-notifications.e2e.spec.js
    cases:
      - >-
        puts the assignment in the person’s inbox and nothing in the
        administrator’s, who made it
      - >-
        opens My Responsibilities of the notice’s own workspace: the
        tenant-relative path, never an absolute link
      - 'says what the notice is about, and names no resource by its id'
      - >-
        tells the person why in the producer’s words: an administrator assigned
        them this responsibility
      - >-
        carries where the assignment applies on the notice itself, as the
        request published it
      - >-
        says the milestone of the channel it did not use, on the delivery
        summary of the notice
      - >-
        marks the notice superseded when the assignment ends, and tells the
        person it ended
      - words the ended notice as an administrator ending the responsibility
      - >-
        tells the delegate who handed them how many responsibilities, and
        confirms to the delegator who acted
      - >-
        words the delegation by who handed it over, to the delegate, and by whom
        it was handed, to the delegator
      - folds five quick assignments of the same responsibility into one notice
      - >-
        cancels the notice of an assignment ended before its dispatch, which the
        test hook delays, and tells nobody it was assigned
      - >-
        refuses a hook value more than 24 hours ahead with a 400 outside
        production
  - provenance: documented
    source: >-
      services-platform:modules/responsibilities/tests/e2e/responsibilities-notifications.e2e.spec.js:suite
      header
    note: >-
      The source header describes the verification boundary and declared
      substitutions.
proof_limit: >-
  Only the named scenario checkpoints have a verified source binding; execution
  has not been attempted.
---

# Responsibility responsibilities notifications checks

## Verification Boundary

This suite checks the module through real local service and database code at the entry points used by its test cases.

## What This Suite Proves

The mapped scenarios identify the capability and feature checkpoints this file exercises. The source test titles preserve the assertion-level evidence.

## What It Does Not Prove

Registration supplies no execution result or conformance decision. Checks beyond the file’s reachable assertions remain unverified, including production configuration.

## Real Dependencies and Test Doubles

The suite uses local integration fixtures. Signing, caches, provider responses or outbound delivery may be supplied by fixtures where the source declares a substitution. The source imports and suite header identify the exact dependencies.

## Must Not Be Doubled

The module behavior under assertion, transaction boundary and database constraint being checked remain real. Fixture setup cannot stand in for the asserted write or refusal.