---
id: TST-PFM-SEC-106
title: Acceptance definitions 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-definitions.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-definitions.integration.spec.js#the
      development fixtures: the acceptance customer’s integrations workspace, definitions and
      personas
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-definitions.integration.spec.js#makes
      the integrations workspace under the customer, live
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-definitions.integration.spec.js#creates
      the desk pair and the five policies and roles
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-definitions.integration.spec.js#gives
      each policy exactly its keys
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-definitions.integration.spec.js#gives
      each role its policy, as a custom customer-scope role of the platform
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-definitions.integration.spec.js#creates
      the six users, each active with its assignment at customer scope
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-definitions.integration.spec.js#reports
      every definition and user existing on the second run
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-definitions.integration.spec.js#changes
      no row on the second run
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-definitions.integration.spec.js#rewrites
      the rules of a policy that already exists with other rules to its definition’s keys
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite controls Cognito at the declared seams; those collaborators remain outside its live
  proof.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/dev-fixtures/acceptance-definitions.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-definitions.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries:
    - Cognito
---
# Acceptance definitions 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 definitions.

## 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 controls Cognito at the declared seams; those collaborators remain outside its live proof.

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