---
id: TST-PFM-SEC-075
title: Security roles eligibility.table 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/db/security-roles-eligibility.table.integration.spec.js
implements:
  - ATS-PFM-SEC-014-06
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/db/security-roles-eligibility.table.integration.spec.js#platform.security_roles:
      the eligibility binding and TTL columns
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/db/security-roles-eligibility.table.integration.spec.js#gives
      a role made without one a TTL of 24 hours
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/db/security-roles-eligibility.table.integration.spec.js#accepts
      a TTL of five minutes, the negative control of the bound below
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/db/security-roles-eligibility.table.integration.spec.js#refuses
      a TTL under five minutes
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/db/security-roles-eligibility.table.integration.spec.js#refuses
      a TTL over thirty days
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/db/security-roles-eligibility.table.integration.spec.js#refuses
      a second role naming the same binding
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/db/security-roles-eligibility.table.integration.spec.js#refuses
      a binding that does not exist
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/db/security-roles-eligibility.table.integration.spec.js#leaves
      the role unbound when its binding is deleted
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The file declares no substituted collaborators.
evidence:
  - >-
    services-platform:modules/security/tests/integration/db/security-roles-eligibility.table.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/db/security-roles-eligibility.table.integration.spec.js
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# Security roles eligibility.table 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 security roles eligibility.table.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

## 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 file declares no substituted collaborators.

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