---
id: TST-PFM-SEC-064
title: Role eligibility request checks
kind: api-lifecycle
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/security/tests/e2e/role-eligibility.e2e.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: 5
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/e2e/role-eligibility.e2e.spec.js#binding a role to
      its rule (PUT /security/{tenantId}/roles/{id}/eligibility, end to end)
  - provenance: test
    source: 'services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#binding'
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#answers the role
      with its binding, its TTL and the counts of the assignments its rule holds now
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#is what the role
      detail answers afterwards
  - provenance: test
    source: 'services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#refusals'
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#refuses a binding of
      another consumer kind as a conflict, naming the kind
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#leaves the role as
      it was after that refusal
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#refuses a built-in
      role as a conflict, because no tenant’s rule may assign Rhythm’s role
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#does not find
      another customer’s role
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#refuses a caller who
      holds only the roles’ read key
  - provenance: test
    source: 'services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#unbinding'
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#answers the role
      unbound, its TTL kept and no assignment of a rule counted
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/role-eligibility.e2e.spec.js#clears the stored
      binding
dependency_evidence: >-
  The local request harness exercises the route dispatcher and the prepared database. The suite
  controls the signing key at the declared seams; those collaborators remain outside its live proof.
evidence:
  - 'services-platform:modules/security/tests/e2e/role-eligibility.e2e.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/e2e/role-eligibility.e2e.spec.js'
  explicit_no_doubles: false
  identified_double_boundaries:
    - the signing key
---
# Role eligibility request checks

## Verification Boundary

The file exercises public request handling through the local service harness. The assertion references identify the source checks for role eligibility.

## 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 local request harness exercises the route dispatcher and the prepared database. The suite controls the signing key at the declared seams; those collaborators remain outside its live proof.

## Must Not Be Doubled

Keep route dispatch, signed-context verification and the exercised service decisions real. A test key can supply signatures, but replacing the authorization decision cannot prove request enforcement.