---
id: TST-PFM-SEC-067
title: Staff separation 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/staff-separation.e2e.spec.js
implements:
  - ATS-PFM-SEC-015-04
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/staff-separation.e2e.spec.js#staff authority
      stops at the system routes (end to end)
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#every route that is
      not a system route
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#is most of the
      macroservice, which is the premise the refusals below are read against
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#refuses the widest
      grant Rhythm holds, every one of them
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#refuses a route that
      names no tenant for want of the permission, which is what the grant really lacks there
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#refuses a route that
      names a tenant at the boundary, because reaching every tenant is a system claim too
  - provenance: test
    source: 'services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#every system route'
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#is the whole of the
      staff surface, which is the premise below
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#differs between the
      two reading roles by exactly the custom query tables the engineer authors
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#admits the Rhythm
      Administrator, who is answered by the operation rather than refused
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#refuses a customer’s
      own Administrator, however complete their grant over their customer
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#tells that
      Administrator they are not staff, rather than that a permission is missing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#refuses a Support
      Representative every staff route their policy does not carry
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/staff-separation.e2e.spec.js#refuses a Software
      Engineer every staff route their grant does not carry, the custom query tables aside
dependency_evidence: >-
  The local request harness exercises the route dispatcher and the prepared database. The file
  declares no substituted collaborators.
evidence:
  - 'services-platform:modules/security/tests/e2e/staff-separation.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/staff-separation.e2e.spec.js'
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# Staff separation request checks

## Verification Boundary

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

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

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