---
id: TST-PFM-TNL-056
title: Platform provisioning request and recovery
kind: api-lifecycle
product_area: platform
module: tenant-lifecycle
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js
implements:
  - ATS-PFM-TNL-001-01
  - ATS-PFM-TNL-001-06
  - ATS-PFM-TNL-002-05
  - ATS-PFM-TNL-002-07
  - ATS-PFM-TNL-003-01
  - ATS-PFM-TNL-003-02
  - ATS-PFM-TNL-003-03
  - ATS-PFM-TNL-003-08
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Run-owned target and comparison workspace records in the prepared test database; owner access is limited to
  fixture arrangement, independent inspection and cleanup of those records.
evidence:
  - 'services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js'
  - >-
    services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports
    ../../../../aws/api/platform-api-handler
  - 'services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports ../../../../db/config'
  - >-
    services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports
    ../../../../db/seeds/integration/seed
  - >-
    services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports
    ../../../../tests/e2e/staff-context
  - >-
    services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports
    ../../db/tenant-seed-applications.table
  - 'services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports ../../db/tenants.table'
  - >-
    services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports
    ../../aws/api/tenants.routes
  - >-
    services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports
    ../../services/lifecycle/participants
  - >-
    services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports
    ../../services/provisioning/provision-tenant-workflow
  - 'services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js imports ../local-provisioning'
binding_scope: >-
  Each implements link names a scenario whose retained cited checks all occur in this file. Partial assertions
  for other scenarios remain evidence only.
partial_scenario_evidence:
  - scenario: ATS-PFM-TNL-003-09
    references:
      - >-
        services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js#leaves the tenant usable
        after the retry
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
  - scenario: ATS-PFM-TNL-005-08
    references:
      - >-
        services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js#leaves the tenant usable
        once the job has run
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
  - scenario: ATS-PFM-TNL-009-01
    references:
      - >-
        services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js#says which participant ran
        for which tenant, and what it did
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
  - scenario: ATS-PFM-TNL-009-02
    references:
      - >-
        services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js#refuses a participant
        nobody has heard of as 400
      - >-
        services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js#may not initialize a
        participant of their own tenant
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
---
# Platform provisioning request and recovery

## Verification Boundary

The suite sends request-shaped events through the local production dispatcher with signed caller contexts and a test database. Its API boundary is real inside the process; it does not call a deployed endpoint or drive a browser.

## What This Suite Proves

Provisioning request and recovery is the inspected subject. The implements links identify scenarios whose cited checks occur in this file. The original test-title references delimit those checks; partial contributions to other combined scenarios remain evidence only.

## What It Does Not Prove

Source inspection supplies no passing run. The suite does not establish console behavior, deployment configuration, complete removal in every application or recovery from a provider failure beyond its declared seams. A local zero inventory covers declared and seeded resources only.

## Real Dependencies and Test Doubles

The local provisioning harness keeps the workflow definition, handler, job engine, Platform participants and database real. It replaces workflow execution with the local runner and supplies remote-application, invitation-provider and message-sender doubles. A completed fixture build therefore does not prove a deployed remote build.

## Must Not Be Doubled

Keep the production service or persistence function and the database constraints, row policies and guarded removal functions under test real. For dispatcher cases, keep route selection and authorization real as well. Provider and remote-application seams must remain explicit and cannot stand in for deployed cross-application qualification.