---
id: TST-PFM-SEC-137
title: Assignments.eligibility.queries database and service checks
kind: integration
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: Use the prepared test database and suite-owned fixture rows; retain shared seed records.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#security
      persistence: eligibility decisions in the grant slice
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#in
      enforce
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#carries
      the latest decision of the binding for the member’s own contact
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#reaches
      the conditioned allow on a fresh eligible decision
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#fails
      the conditioned allow closed on a stale decision
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#fails
      the conditioned allow closed on a fresh ineligible decision
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#fails
      the conditioned allow closed when the contact has no decision, and carries none
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#keeps
      the conditioned deny in force on a stale decision
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#keeps
      the conditioned deny in force when the contact has no decision
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#lifts
      the conditioned deny only on a fresh ineligible decision, the premise of the two cases above
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#in
      off and shadow
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#adds
      nothing to the slice in off, the default when the variable is unset
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#answers
      in shadow what off answers: the slice carries no decision
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#logs
      in shadow every key whose answer the decisions would change, with both answers
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#logs
      nothing in shadow for a member whose decisions change no answer
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#the
      signed slice
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#signs
      a slice carrying up to twenty eligibility conditions
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#refuses
      a slice carrying more than twenty eligibility conditions as grant_slice_too_large
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#a
      condition only a live check can answer
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#is
      refused 403 before the handler when the route does not declare the key in evaluates
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js#reaches
      the handler when the route declares the key in evaluates, the control for that refusal
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite controls the clock at the declared seams; those collaborators remain outside its live
  proof.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  The file has no scenario binding established by this examination. Its executable checks remain
  registered without assigning them broader acceptance coverage.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/persistence/assignments.eligibility.queries.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries:
    - the clock
---
# Assignments.eligibility.queries database and service checks

## Verification Boundary

The file exercises database or service behavior through the local integration harness. The assertion references identify the source checks for assignments.eligibility.queries.

## What This Suite Proves

The file supplies executable engineering checks for the named subject. No complete acceptance scenario is inferred from the file’s existence.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite controls the clock at the declared seams; those collaborators remain outside its live proof.

## Must Not Be Doubled

Keep the queried database, applicable constraints and transaction boundaries real. Provider substitutes cannot establish delivery, cloud execution or cross-service recovery.