---
id: TST-PFM-SEC-115
title: Evaluated route keys 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/evaluated-route-keys.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/evaluated-route-keys.integration.spec.js#the
      grant slice of a route that evaluates another application's key
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/evaluated-route-keys.integration.spec.js#what
      the route asks for
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/evaluated-route-keys.integration.spec.js#is
      allowed by Platform’s own key and evaluates the purpose key of another application
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/evaluated-route-keys.integration.spec.js#puts
      that key in the built-in CRM Administrator policy, so a customer administrator really holds it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/evaluated-route-keys.integration.spec.js#the
      slice the authorizer resolves for it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/evaluated-route-keys.integration.spec.js#carries
      the rule that allows the evaluated key, naming the policy it came from
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/evaluated-route-keys.integration.spec.js#carries
      the key the route is allowed by in the same slice, so one request asks once
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/evaluated-route-keys.integration.spec.js#leaves
      the CRM rule out when only the route’s required keys are asked for, which was the defect
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The file declares no substituted collaborators.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/evaluated-route-keys.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/evaluated-route-keys.integration.spec.js
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# Evaluated route keys 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 evaluated route keys.

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

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