---
id: TST-PFM-ELG-490
title: Eligibility subject existence checks
kind: unit
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/eligibility/tests/unit/subject-existence.spec.js
implements:
  - ATS-PFM-ELG-008-02
environment: mock
implementation_state: implemented
latest_result: not-run
conformance: not-verified
estimated_minutes: 1
isolation: One process with suite-local inputs.
evidence:
  - provenance: test
    source: 'services-platform:modules/eligibility/tests/unit/subject-existence.spec.js'
    cases:
      - names a slot whose entity was asked about and not answered
      - names no slot whose entity a read answered
      - names no slot whose kind no read asked about
      - names no slot left empty
      - 'names only the missing one of two slots, in the slots’ order'
      - answers the fold’s own evaluation when no subject is missing
      - >-
        answers an eligible fold indeterminate, UNKNOWN, subject_not_found when
        a subject is missing
      - >-
        answers an ineligible fold indeterminate too, with subject_not_found its
        one reason
      - keeps the fold’s trace for the explanation
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/unit/subject-existence.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 subject existence checks

## Verification Boundary

This suite checks isolated decisions and validation using the imported inputs. It cannot establish a complete service or browser lifecycle.

## 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. Passing isolated checks does not establish deployed dependencies or cross-application delivery.

## Real Dependencies and Test Doubles

The suite exercises its real module dependencies and declares no test doubles. Its source header and imports identify the database, transaction and service boundaries it uses.

## Must Not Be Doubled

The decision or validator being asserted remains real; returning the expected answer from a substitute defeats the check.