---
id: TST-PFM-ELG-441
title: Eligibility validate definition 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/model/validate-definition.integration.spec.js
implements:
  - ATS-PFM-ELG-001-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/model/validate-definition.integration.spec.js
    cases:
      - accepts a reference to a published definition
      - answers a reference to an archived definition as missing
      - answers a reference to a definition with only a draft as missing
      - >-
        answers a reference that pins a version the definition has only as a
        draft as missing
      - answers a reference to another tenant’s definition as missing
      - >-
        answers a draft that reaches itself through a published reference as a
        cycle
      - answers a fact no binding supplies as unknown
      - accepts a fact the consumer kind of a binding of the definition supplies
      - accepts a custom field of the tenant’s contacts
      - >-
        answers a field the tenant’s contacts do not have as invalid args,
        naming it
      - 'answers the field as unknown in another tenant, which has no such field'
      - answers a primary subject of another kind than the definition’s
      - 'records each condition type, referenced definition and fact'
      - records a pinned reference with its version number
      - records nothing for a reference that was not found
      - is what a saved draft records in the dependency graph
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/services/model/validate-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.
---

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