---
id: TST-PFM-ELG-483
title: Eligibility inventory checks
kind: unit
product_area: platform
module: eligibility
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/eligibility/tests/unit/migration/inventory.spec.js
implements: []
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/migration/inventory.spec.js'
    cases:
      - 'counts the criteria of each host, with its subject convention or null for an unknown host'
      - 'counts the sections used, overall and per host'
      - 'counts every advanced rule leaf by fact, operator and path, nested groups included'
      - lists every expression text and every Lambda id with the records that use it
      - lists every organization switch with its host’s subject convention
      - counts the unknown keys and lists the criteria without the 1.0 shape
      - 'renders the same report as Markdown, a section per finding'
      - reports an empty tenant with every count at zero
  - provenance: documented
    source: 'services-platform:modules/eligibility/tests/unit/migration/inventory.spec.js:suite header'
    note: The source header describes the verification boundary and declared substitutions.
proof_limit: >-
  No complete capability or feature scenario is mapped to this file; case-level ownership remains a
  coverage finding.
---

# Eligibility inventory 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 file contains executable checks, but no complete scenario mapping is established here. Its source test titles identify the remaining mapping work.

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