---
id: TST-PFM-ELG-395
title: Attention settings 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/settings.integration.spec.js
implements:
  - ATS-PFM-ELG-020-02
  - ATS-PFM-ELG-020-03
  - ATS-PFM-ELG-020-04
  - ATS-PFM-ELG-020-05
  - ATS-PFM-ELG-020-06
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/settings.integration.spec.js
    cases:
      - writes the settings the first time without a version and audits it
      - replaces them at the version read
      - 'refuses a stale version, the row unchanged'
      - 'refuses a value outside its declared bounds, naming it'
      - refuses a surface the definition does not have
      - refuses a rank adjustment on a definition that is not tenant-adjustable
      - refuses a template override that names an undeclared fact
      - accepts a template override that renders the examples
      - >-
        audits a change of the template overrides and the rank adjustment with
        both before and after
      - refuses a reminder cadence shorter than an hour
      - >-
        refuses an escalation on a definition that does not let the tenant
        change it
      - refuses an escalation to a role no product role carries
  - provenance: documented
    source: >-
      services-platform:modules/attention/tests/integration/services/persistence/settings.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 settings 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.