---
id: TST-PFM-ELG-436
title: Eligibility usage 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/governance/usage.integration.spec.js
implements:
  - ATS-PFM-ELG-002-05
  - ATS-PFM-ELG-002-07
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/governance/usage.integration.spec.js
    cases:
      - names the definition and the version it last published
      - >-
        groups the bindings by consumer kind in kind order, each labelled from
        the registry and counted
      - >-
        answers each binding with its consumer, mode, status, fail policy and
        pin
      - >-
        answers each reference with its pin and the referencing definition’s own
        usage, in key order
      - answers an unused definition with no bindings and no references
      - 'refuses a definition the tenant does not have, 404'
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/services/governance/usage.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 usage 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.