---
id: TST-PFM-SEC-048
title: Application access 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/application-access.e2e.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: 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/application-access.e2e.spec.js#the application
      access step as a Platform function evaluates it (end to end)
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#with the step off,
      as an environment that has not been told anything runs it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#serves the other
      application's route for a caller without its access key
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#writes no shadow
      line, so the lines the shadow case reads are the mode and not the request
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#with the step in
      shadow, as every environment deploys it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#serves the other
      application's route for a caller without its access key: nobody's access changes
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#warns once, naming
      the key, the tenant, the reason and the caller, so an operator can find the person
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#says nothing about
      a caller who does hold the access key, and serves them as before
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#says nothing about
      a Platform route, which the step never gates, though the caller holds no Platform access key
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#with the step
      enforcing, which this test alone asks for
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#refuses the other
      application's route with 403 and the code a client branches on
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#serves the same
      route for the caller who holds the access key
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#serves the
      Platform route for the caller it refused above, because Platform is exempt
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#the mode the
      deployed functions are given
  - provenance: test
    source: >-
      services-platform:modules/security/tests/e2e/application-access.e2e.spec.js#leaves the process
      environment as it found it, so no other suite inherits a mode
dependency_evidence: >-
  The local request harness exercises the route dispatcher and the prepared database. The suite’s
  own dependency setup determines which external collaborators are controlled; registration alone
  does not certify them as live.
evidence:
  - 'services-platform:modules/security/tests/e2e/application-access.e2e.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/e2e/application-access.e2e.spec.js'
  explicit_no_doubles: false
  identified_double_boundaries: []
---
# Application access request checks

## Verification Boundary

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

## 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 local request harness exercises the route dispatcher and the prepared database. The suite’s own dependency setup determines which external collaborators are controlled; registration alone does not certify them as live.

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