---
id: TST-PFM-ELG-422
title: Eligibility dependencies table checks
kind: integration
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/eligibility/tests/integration/db/eligibility-dependencies.table.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
conformance: not-verified
estimated_minutes: 5
isolation: Prepared local test database with suite-owned fixture keys and cleanup.
evidence:
  - provenance: test
    source: >-
      services-platform:modules/eligibility/tests/integration/db/eligibility-dependencies.table.integration.spec.js
    cases:
      - modules/eligibility/db/eligibility-dependencies.table.ts
      - accepts a dependency with an empty detail by default
      - >-
        refuses the same kind and target twice for one version, by the primary
        key
      - accepts the same target under another kind
      - 'refuses a kind outside the four, by the kind check'
      - 'refuses a detail that is not an object, by the detail check'
      - 'refuses a version that does not exist, by the version foreign key'
      - goes with its version when the version is deleted
      - >-
        refuses a blank target: the trigger nulls it and the column refuses the
        null
      - 'holds both tenants’ dependencies, read as the owner'
      - reads only the acting tenant’s dependencies
      - reads nothing at all with no tenant
      - 'refuses a write for another tenant, by the policy'
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/db/eligibility-dependencies.table.integration.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 dependencies table checks

## Verification Boundary

This suite checks the module through real local service and database code at the entry points used by its test cases.

## 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. Checks beyond the file’s reachable assertions remain unverified, including production configuration.

## 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 module behavior under assertion, transaction boundary and database constraint being checked remain real. Fixture setup cannot stand in for the asserted write or refusal.