---
id: TST-PFM-ELG-494
title: Responsibility responsibility notices checks
kind: integration
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/responsibilities/tests/integration/services/notices/responsibility-notices.integration.spec.js
implements:
  - ATS-PFM-ELG-013-12
  - ATS-PFM-ELG-014-04
  - 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/integration/services/notices/responsibility-notices.integration.spec.js
    cases:
      - >-
        publishes one assigned request to the person, with the data the template
        reads and the occurrence’s supersede key
      - >-
        holds the notice until the instant the test hook gives, and holds
        nothing without it
      - >-
        names no resource by its id: a tenant assignment is the organization and
        a resource assignment is its type and id for the console to name
      - 'publishes nothing for a role default, which is nobody’s assignment'
      - >-
        publishes nothing when the administrator assigns it to themself: they
        hear nothing for their own acts
      - >-
        publishes nothing when the assignment is refused, and the refusal leaves
        nothing behind
      - >-
        leaves out a notice the library refuses, logging it, while the
        assignment stands
      - >-
        withdraws the assigned notice by its supersede key and tells the person
        it ended
      - >-
        withdraws the notice but tells nobody when the person ends their own
        assignment
      - publishes nothing when the end is refused for a stale version
      - >-
        tells the delegate once and confirms to the person who delegated, even
        though they are the one acting
      - >-
        is about the responsibility only when the request hands over one, never
        about a mix
      - holds both notices of a delegation until the instant the test hook gives
      - >-
        tells the delegate once for “delegate all mine”, counting every
        assignment, and confirms once
      - publishes nothing when “delegate all mine” finds nothing to hand over
      - >-
        confirms to the holder, not the manager, when a manager delegates
        someone else’s assignment
      - publishes nothing when the delegation is refused
      - >-
        wakes the dispatcher’s live alias once, asynchronously, after the
        assignment has committed
      - wakes it after a delegation has committed both its notices
      - does not wake it for an operation that published nothing
  - provenance: documented
    source: >-
      services-platform:modules/responsibilities/tests/integration/services/notices/responsibility-notices.integration.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 responsibility notices 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.