---
id: TST-PFM-SEC-105
title: Acceptance administrator 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/dev-fixtures/acceptance-administrator.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/dev-fixtures/acceptance-administrator.integration.spec.js#the
      development fixtures: the acceptance Administrator policy and the CRM user role
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-administrator.integration.spec.js#ensureAcceptanceAdministratorPolicy
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-administrator.integration.spec.js#creates
      the customer’s Administrator policy and role on the first run
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-administrator.integration.spec.js#allows
      exactly the assignable keys of the current catalogue
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-administrator.integration.spec.js#attaches
      the policy to the role
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-administrator.integration.spec.js#reports
      everything existing and changes no version when the catalogue has nothing new
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-administrator.integration.spec.js#adds
      a key a peer’s manifest added since the last run, and a staff-only key never
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-administrator.integration.spec.js#removes
      a key the catalogue no longer holds
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-administrator.integration.spec.js#ensureCrmUserRole
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-administrator.integration.spec.js#makes
      a custom customer-scope role of CRM, holding no policy while CRM’s User policy is not
      published, once
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/dev-fixtures/acceptance-administrator.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/dev-fixtures/acceptance-administrator.integration.spec.js
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# Acceptance administrator 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 acceptance administrator.

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