---
id: TST-PFM-ELG-390
title: Attention evaluate definition 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/evaluate/evaluate-definition.integration.spec.js
implements:
  - ATS-PFM-ELG-015-06
  - ATS-PFM-ELG-016-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/evaluate/evaluate-definition.integration.spec.js
    cases:
      - >-
        publishes one item per matching record with its facts and the fixed
        audience, and records the run
      - >-
        resolves the item of a record the next run no longer matches (the
        tenant’s setting narrowed it)
      - 'stops a run past its cap as over_capacity, resolving nothing'
      - 'refuses an eligibility binding, recording the run as failed'
      - >-
        publishes one item per open row, addressed to the administrators, about
        the responsibility
      - resolves the item once the row is cleared
  - provenance: documented
    source: >-
      services-platform:modules/attention/tests/integration/services/evaluate/evaluate-definition.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 evaluate definition 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.