---
id: TST-PFM-ELG-509
title: Responsibility responsibilities notifications checks
kind: unit
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/responsibilities/tests/unit/responsibilities-notifications.spec.js
implements: []
environment: mock
implementation_state: implemented
latest_result: not-run
conformance: not-verified
estimated_minutes: 1
isolation: One process with suite-local inputs.
evidence:
  - provenance: test
    source: >-
      services-platform:modules/responsibilities/tests/unit/responsibilities-notifications.spec.js
    cases:
      - 'are four definitions of the platform application, valid as a manifest'
      - >-
        are assignments, channel configurable, at least one channel, in-app and
        e-mail by default, to a user
      - >-
        make assigned important, withdrawn with its occurrence, and opened by an
        Open responsibility action
      - >-
        have closed data schemas their examples satisfy and templates that
        render them within the limits, in every channel
      - 'tell the person what they were assigned, where, for how long and by whom'
      - >-
        carry the tenant-relative path in the in-app record and the absolute
        link in every other channel
      - >-
        leave the end out of an assignment that has none, and say no resource id
        for a resource scope
      - 'tell the person an assignment ended, by whom'
      - >-
        tell the delegate who handed them how many responsibilities until when,
        in their own zone
      - 'say "1 responsibility" for one, and give the reason when there is one'
      - confirm to the person who delegated who now covers how many
      - keep every title within 140 characters even for a long name
  - provenance: documented
    source: >-
      services-platform:modules/responsibilities/tests/unit/responsibilities-notifications.spec.js:suite
      header
    note: >-
      The source header describes the verification boundary and declared
      substitutions.
proof_limit: >-
  No complete capability or feature scenario is mapped to this file; case-level
  ownership remains a coverage finding.
---

# Responsibility responsibilities notifications checks

## Verification Boundary

This suite checks isolated decisions and validation using the imported inputs. It cannot establish a complete service or browser lifecycle.

## What This Suite Proves

The file contains executable checks, but no complete scenario mapping is established here. Its source test titles identify the remaining mapping work.

## What It Does Not Prove

Registration supplies no execution result or conformance decision. Passing isolated checks does not establish deployed dependencies or cross-application delivery.

## Real Dependencies and Test Doubles

The suite exercises its real module dependencies and declares no test doubles. Its source header and imports identify the database, transaction and service boundaries it uses.

## Must Not Be Doubled

The decision or validator being asserted remains real; returning the expected answer from a substitute defeats the check.