---
id: TST-PFM-ELG-396
title: Attention states checks
kind: integration
product_area: platform
module: eligibility
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/attention/tests/integration/services/persistence/states.integration.spec.js
implements:
  - ATS-PFM-ELG-018-02
  - ATS-PFM-ELG-018-03
  - ATS-PFM-ELG-018-05
  - ATS-PFM-ELG-018-06
  - ATS-PFM-ELG-018-09
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/states.integration.spec.js
    cases:
      - acknowledges an item and records attention.acknowledged against its definition
      - snoozes a required item within its bound and counts the snooze
      - 'refuses a required item’s snooze past its bound as snooze_limit, the state unchanged'
      - 'refuses dismissing a required item as not_dismissable, writing no trail'
      - 'unsnoozes, recorded as attention.snoozed with action unsnooze'
      - dismisses an advisory and records attention.dismissed
      - advances the state’s version with each action
  - provenance: documented
    source: >-
      services-platform:modules/attention/tests/integration/services/persistence/states.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 states 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 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 module behavior under assertion, transaction boundary and database constraint being checked remain real. Fixture setup cannot stand in for the asserted write or refusal.