---
id: TST-PFM-ELG-467
title: Eligibility alarm inputs 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/alarm-inputs.spec.ts
implements:
  - ATS-PFM-ELG-012-01
  - ATS-PFM-ELG-012-02
  - ATS-PFM-ELG-012-03
  - ATS-PFM-ELG-012-04
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/alarm-inputs.spec.ts'
    cases:
      - >-
        reads the engine’s four metrics in the three alarms over Rhythm metrics
        (premise)
      - 'finds a metric no emitter names, so the check below is not vacuous'
      - >-
        finds an emitted metric read under a dimension the emitter never writes,
        so the dimension check is not vacuous
      - 'reads only metrics some code path emits, under the emitter’s dimensions'
      - >-
        reads the population run’s failure under the service its task function
        records it as (DEF-ELIG-0675)
      - >-
        reads the circuit refusals under both services that evaluate: the API
        function’s and the population task’s
      - reads the evaluation counts under the API function’s service
      - watches the age of a queue the macroservice creates
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/unit/alarm-inputs.spec.ts: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 alarm inputs 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.