---
id: TST-PFM-ELG-466
title: Eligibility registry snapshot 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/registry/registry-snapshot.integration.spec.js
implements:
  - ATS-PFM-ELG-006-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/registry/registry-snapshot.integration.spec.js
    cases:
      - 'answers each active type as the package declared it, keyed by its key'
      - 'answers a deprecated type, which still evaluates, with its status'
      - leaves a withdrawn type out
      - 'answers each consumer kind as declared, with its status'
      - >-
        stamps the snapshot with the newest registration instant, the
        withdrawal’s, as ISO 8601 UTC
      - answers a snapshot the package’s own schema accepts
      - answers the same snapshot through registrySnapshot
      - >-
        keeps answering what it read for 60 seconds, though a type was written
        since
      - reads the tables again once the 60 seconds are over
      - reads the tables again after a registration commits in this process
      - 'is the constant empty, a non-empty stamp the package accepts'
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/services/registry/registry-snapshot.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 registry snapshot 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.