---
id: TST-PFM-ELG-475
title: Eligibility definition key alias 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/definition-key-alias.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/definition-key-alias.spec.js
    cases:
      - repeats the id as key and keeps the other properties
      - gives every explorer row its key and keeps the cursor
      - >-
        gives the definition of a create or duplicate answer its key, leaving
        the rest
      - 'answers a delete as id, key and deleted'
      - takes id
      - takes key when id is absent
      - takes key when id is null
      - accepts both when they are equal
      - 'refuses both when they differ, naming both'
      - 'refuses neither, naming id'
      - accepts a create naming key only
      - accepts a create naming id only
      - refuses a key outside the configuration-id grammar
      - accepts a duplicate naming key only
      - refuses a duplicate key outside the configuration-id grammar
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/unit/definition-key-alias.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 definition key alias 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.