---
id: TST-PFM-SEC-094
title: HQ roles 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/catalog/hq-roles.integration.spec.js
implements:
  - ATS-PFM-SEC-016-06
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/catalog/hq-roles.integration.spec.js#security
      catalog: listHqRoles, the HQ roles and what each one carries
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/catalog/hq-roles.integration.spec.js#answers
      the HQ roles the catalog holds, by name
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/catalog/hq-roles.integration.spec.js#answers
      each role with the description the catalog stores for it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/catalog/hq-roles.integration.spec.js#leaves
      out a staff role the catalog has no row for, rather than inventing one
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/catalog/hq-roles.integration.spec.js#expands
      a wildcard pattern to every concrete key of the catalog, sorted
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/catalog/hq-roles.integration.spec.js#answers
      the keys of a role's attached policy, which is where Rhythm Support's come from
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/catalog/hq-roles.integration.spec.js#never
      answers a staff-only key to a role whose policy does not reach one
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/catalog/hq-roles.integration.spec.js#answers
      the staff-only key to the role whose pattern does reach it
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/catalog/hq-roles.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/catalog/hq-roles.integration.spec.js
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# HQ roles 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 HQ roles.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

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