---
id: TST-PFM-SEC-248
title: Workspace provisioning jobs.queries 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/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.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/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#reading
      a tenant provisioning job
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      the job by its id, with the contract’s fields and this family’s own
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      nothing for a job id nobody made
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      null for a request that named no first administrator, rather than leaving the fields out
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      the tenant’s most recent provisioning, not its first
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      nothing for a tenant that was never provisioned
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      the tenant’s unfinished provisioning
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      no unfinished provisioning once the job has settled
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      the job a submission identity already made
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      nothing for a submission identity nobody has used
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#the
      tenants stranded in provisioning behind a failed job
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      a tenant still provisioning whose latest job failed, with that job and its summary
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#does
      not answer a tenant whose provisioning is still under way
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#does
      not answer a tenant whose failed provisioning was followed by a newer one
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#does
      not answer a tenant that has already left provisioning
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#answers
      no more tenants than the limit
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#the
      domain fields a submission carries
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#reads
      what the submission named
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#defaults
      the mode to sandbox when the submission named none
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#refuses
      a submission that names no tenant
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#refuses
      a mode a tenant is never provisioned into
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js#refuses
      a first administrator with an address and no name
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite controls workflow execution at the declared seams; those collaborators remain outside
  its live proof.
evidence:
  - >-
    services-platform:modules/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.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/tenants/tests/integration/services/persistence/tenant-provisioning-jobs.queries.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries:
    - workflow execution
---
# Workspace provisioning jobs.queries 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 workspace provisioning jobs.queries.

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