---
id: TST-PFM-ELG-489
title: Eligibility sql prefix 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/sql-prefix.spec.js
implements:
  - ATS-PFM-ELG-011-03
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/sql-prefix.spec.js'
    cases:
      - is the sql condition itself for a rule of one sql condition
      - keeps the sql side of an and whose other side reads a provider
      - prunes no one for an or one of whose branches depends on a provider
      - prunes no one for a rule that reads only providers
      - negates a negated sql condition as a negated group
      - >-
        prunes no one for a negated and of a sql condition and a provider, since
        not of unknown is unknown
      - >-
        keeps the negated sql side of a negated or whose other side reads a
        provider
      - combines two sql conditions of an or into one or group
      - >-
        treats an aggregate condition as unknown, so an and keeps only its
        boolean side
      - answers everyone when either of two prefixes prunes no one
      - answers the other prefix when one prunes everyone
      - >-
        names who became eligible, who stopped being eligible, and counts who
        stayed
      - lists the newly eligible in id order whatever order the sets came in
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/unit/sql-prefix.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 sql prefix 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 runs isolated checks; its imported fixtures and injected collaborators define the substitutions. The source imports and suite header identify the exact dependencies.

## Must Not Be Doubled

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