---
id: TST-PFM-ELG-511
title: Eligibility derived assignment reconciles checks
kind: integration
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/security/tests/integration/services/dispatch/derived-assignment-reconciles.integration.spec.js
implements:
  - ATS-PFM-ELG-010-05
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/security/tests/integration/services/dispatch/derived-assignment-reconciles.integration.spec.js
    cases:
      - >-
        is a system route asking for the staff-only
        platform.eligibility.reconcile
      - refuses more than 100 subjects
      - refuses a subject kind the role assignment does not take
      - 'takes each subject once, in the order first given'
      - >-
        queues one row and answers its work id, and a second request for the
        waiting subject answers the same id
      - >-
        publishes the row as an item of identifiers only, and deletes it once
        the queue accepted it
      - 'reconciles the subject on delivery, acknowledging the message'
      - 'grants nothing twice on a redelivery: the same row, confirmed again'
      - >-
        gives the failed item back to SQS and acknowledges the one it cannot
        read
      - stays queued for the next run
  - provenance: documented
    source: >-
      services-platform:modules/security/tests/integration/services/dispatch/derived-assignment-reconciles.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 derived assignment reconciles 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.