---
id: TST-PFM-ELG-460
title: Eligibility simulations checks
kind: integration
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/eligibility/tests/integration/services/persistence/simulations.integration.spec.js
implements:
  - ATS-PFM-ELG-011-08
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/eligibility/tests/integration/services/persistence/simulations.integration.spec.js
    cases:
      - >-
        creates the simulation queued, kept thirty calendar days in the tenant’s
        zone
      - 'refuses to simulate a version that is not a draft, and creates nothing'
      - refuses a baseline of another definition
      - records the impact as the simulation runs
      - settles the simulation with its reference impact
      - 'refuses new impact once the simulation has settled, and leaves it'
      - refuses a move back to queued
      - >-
        expires the settled simulation once its time has come, and only in its
        own tenant
      - refuses a simulation of another tenant as not found
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/services/persistence/simulations.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.
---

# Eligibility simulations 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.