---
id: TST-PFM-SEC-155
title: Permissions 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/persistence/permissions.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/persistence/permissions.integration.spec.js#security
      persistence: security_permissions
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#upsertPermission
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#writes
      a declaration, splitting the key into its three segments so "every key of this app" is an
      index scan
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#records
      what a key is for: its tier, whether it is sensitive, staff-only, and the resource that scopes
      it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#declaring
      the same key again changes nothing and leaves the version where it was
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#declaring
      it differently updates it in place and bumps the version
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#refuses
      a key that is not <app>.<resource>.<action>, naming the key rather than a constraint
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#retirePermissionsNotIn
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#retires
      the keys a release no longer declares, and keeps the row so a rule that names it stays legible
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#retires
      nothing, and writes nothing, when the release declares everything that is active
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#never
      retires another app's keys: a release speaks only for the apps it declares
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#the
      key helpers the grant slice rests on
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#splits
      a key and refuses one that is not a key
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#matches
      a pattern one whole segment at a time, with the lone star matching everything
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#pads
      a short pattern that ends in a star, so platform.* and platform.*.* are the same pattern
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#answers
      whether any pattern covers any key, which is the filter a grant slice applies to a rule
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#turns
      a row into the definition the catalog and the evaluator share, leaving absent facts out
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#the
      seeded catalog
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/persistence/permissions.integration.spec.js#holds
      every key the integration fixture declares, with the staff-only one marked
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  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/integration/services/persistence/permissions.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/persistence/permissions.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries: []
---
# Permissions 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 permissions.

## 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 suite’s own dependency setup determines which external collaborators are controlled; registration alone does not certify them as live.

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