---
id: TST-PFM-SEC-053
title: Derived assignments 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/derived-assignments.e2e.spec.js
implements:
  - ATS-PFM-SEC-014-01
  - ATS-PFM-SEC-014-05
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/derived-assignments.e2e.spec.js#a
      committee-derived, contact-keyed grant reaching a portal member (end to end)
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/derived-assignments.e2e.spec.js#is allowed by the
      authorizer inside its validity, for the tenant of the grant
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/derived-assignments.e2e.spec.js#signs the derived
      grant into the member’s slice, with its resource scope and window
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/derived-assignments.e2e.spec.js#serves the
      protected route for the unit the grant names, inside its validity
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/derived-assignments.e2e.spec.js#refuses another
      unit, which the grant does not name
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/derived-assignments.e2e.spec.js#refuses the same
      still-unexpired context once valid_until has passed, because validity is read per request
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/derived-assignments.e2e.spec.js#is refused by the
      authorizer itself after valid_until, for want of a grant in force
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/derived-assignments.e2e.spec.js#lists the derived
      grant in the member’s own access document, saying it is derived by committees from its key
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/derived-assignments.e2e.spec.js#is refused once
      the member is no longer linked to the contact, so the link is what carries the grant
dependency_evidence: >-
  The local request harness exercises the route dispatcher and the prepared database. The suite
  controls Cognito, the signing key, registry reads at the declared seams; those collaborators
  remain outside its live proof.
evidence:
  - 'services-platform:modules/security/tests/e2e/derived-assignments.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/derived-assignments.e2e.spec.js'
  explicit_no_doubles: false
  identified_double_boundaries:
    - Cognito
    - the signing key
    - registry reads
---
# Derived assignments request checks

## Verification Boundary

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

## 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 Cognito, the signing key, registry reads 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.