---
id: TST-PFM-ELG-496
title: Responsibility assignments queries 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/persistence/assignments.queries.integration.spec.js
implements:
  - ATS-PFM-ELG-013-07
  - ATS-PFM-ELG-013-10
  - ATS-PFM-ELG-013-11
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/persistence/assignments.queries.integration.spec.js
    cases:
      - >-
        answers the derivation sync with what it inserted, and a second
        identical sync with nothing changed
      - >-
        answers the unit’s primary at specificity 0, not covering, with its name
        and address
      - 'answers the delegate of the unit’s primary, covering for them'
      - >-
        leaves the tenant-wide holder out when the unit has its own primary and
        coverage is when_unheld
      - >-
        answers the tenant-wide holder as covering at another unit, which nobody
        holds
      - >-
        answers the wider holder too, flagged covering, when the definition’s
        coverage is always
      - >-
        answers the fallback’s holders, every one covering, when nobody holds
        the key at any scope of the chain
      - expands a role-default row into the role’s holders
      - >-
        answers a user’s effective rows with via, their delegation from a
        colleague included
      - 'answers the role-default rows of a role the user holds, naming the role'
      - names the role of a role-default row in the effective answer
      - leaves the role label empty on a direct row
      - >-
        names the role of a role-default assignment in the list, and leaves a
        direct one without
      - leaves out an assignment whose window has not opened
      - 'lists the assignments of one definition in id order, one page at a time'
      - lists the assignments at one scope
  - provenance: documented
    source: >-
      services-platform:modules/responsibilities/tests/integration/services/persistence/assignments.queries.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 assignments queries 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.