---
id: TST-PFM-SEC-162
title: Roles.eligibility 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/roles.eligibility.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/roles.eligibility.integration.spec.js#security
      persistence: a role bound to an eligibility rule
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#setRoleEligibility
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#stores
      the binding and the TTL on the role, and moves its version
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#refuses
      a binding of another kind, leaving the role unchanged
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#refuses
      a binding that assigns another role, leaving the role unchanged
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#refuses
      a binding the tenant does not have
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#refuses
      a TTL under five minutes before anything is read
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#unbinding
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#clears
      the binding and keeps the TTL
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#takes
      the role out of the tenant’s rule-bound roles
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#listRuleBoundRoles
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#answers
      the role with its binding, the binding’s definition and the TTL in the binding’s tenant
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#answers
      nothing in another tenant
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#derivedAssignmentCounts
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#counts
      the rows its binding derived that apply now and those ending within 24 hours, never the manual
      one or another key’s
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#stops
      counting one once it has expired
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.integration.spec.js#counts
      nothing before any has begun
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite’s own dependency setup determines which external collaborators are controlled;
  registration alone does not certify them as live.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/persistence/roles.eligibility.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/roles.eligibility.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries: []
---
# Roles.eligibility 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 roles.eligibility.

## 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’s own dependency setup determines which external collaborators are controlled; registration alone does not certify them as live.

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