---
id: TST-PFM-ELG-393
title: Attention items queries checks
kind: integration
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/attention/tests/integration/services/persistence/items.queries.integration.spec.js
implements:
  - ATS-PFM-ELG-014-06
  - ATS-PFM-ELG-017-02
  - ATS-PFM-ELG-017-04
  - ATS-PFM-ELG-017-06
  - ATS-PFM-ELG-017-08
  - ATS-PFM-ELG-017-09
  - ATS-PFM-ELG-017-13
  - ATS-PFM-ELG-017-14
  - ATS-PFM-ELG-020-02
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/attention/tests/integration/services/persistence/items.queries.integration.spec.js
    cases:
      - north
      - south
      - >-
        reaches the direct holder at the item’s resource scope, as a
        responsibility at a resource
      - >-
        does not reach a tenant-wide holder where somebody holds the narrower
        scope (coverage when_unheld)
      - >-
        reaches the tenant-wide holder as covering where nobody holds the item’s
        scope
      - 'reaches the holders of a role default at the tenant, via the role'
      - >-
        hides a backup while the primary is present (backup_visibility
        when_primary_absent)
      - 'reaches a delegate through the delegation, naming whom they cover for'
      - reaches a user audience’s user alone
      - 'reaches a role audience’s holders, and not a user without the role'
      - >-
        answers an item reaching the viewer through two audiences once, with the
        better reason
      - ranks a required overdue item before an advisory one
      - pages by the keyset without repeating or dropping an item
      - >-
        leaves out an item the viewer snoozed, and shows it when asked for
        snoozed items
      - leaves out an item the viewer dismissed
      - >-
        answers the item rendered, with why it exists, why the viewer and when
        it changes
      - 'names the reason’s scope by words, never by the unit’s id'
      - labels each fact it carries with the definition’s label
      - 'tells when it was last checked as short local text, with no timestamp'
      - answers 404 for an item the viewer is not addressed by
      - >-
        groups the viewer’s items by definition and urgency, with counts and
        group titles
      - >-
        says all_clear to a viewer who holds responsibilities and has nothing
        open
      - >-
        says no_responsibilities to a viewer who holds none and is addressed by
        nothing
      - >-
        says nothing_enabled where the tenant has disabled every definition on
        the console
      - 'answers every open item about a record, marking the viewer’s own'
      - 'refuses a portal caller: the portal read is held'
      - 'reads nothing of the tenant without a tenant: the policy fails closed'
      - 'pages the console items of a viewer through the read service, rendered'
  - provenance: documented
    source: >-
      services-platform:modules/attention/tests/integration/services/persistence/items.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.
---

# Attention items 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.