---
id: TST-PFM-SEC-090
title: Authorizer 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/authorizer-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/authorizer-eligibility.integration.spec.js#the
      authorizer signs the eligibility decisions a portal user’s grant needs
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/authorizer-eligibility.integration.spec.js#signs
      the decision in enforce, and the context verifies carrying it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/authorizer-eligibility.integration.spec.js#lets
      the evaluator answer the route from the verified slice in enforce
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/authorizer-eligibility.integration.spec.js#signs
      no decision in off, though the slice carries the condition
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite controls Cognito, the clock, the signing key, registry reads at the declared seams;
  those collaborators remain outside its live proof.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/authorizer-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/authorizer-eligibility.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries:
    - Cognito
    - the clock
    - the signing key
    - registry reads
---
# Authorizer 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 authorizer 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 controls Cognito, the clock, the signing key, registry reads 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.