---
id: TST-PFM-TNL-079
title: Platform existing-workspace initialization
kind: integration
product_area: platform
module: tenant-lifecycle
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/tenants/tests/integration/services/provisioning/initialize-tenant.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: 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/integration/services/provisioning/initialize-tenant.integration.spec.js
  - >-
    services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js
    imports ../../../../services/provisioning/initialize-tenant
  - >-
    services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js
    imports ../../../../services/persistence/tenants
  - >-
    services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js
    imports ../../../../services/lifecycle/participants
  - >-
    services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js
    imports ../../provisioning-support
binding_scope: >-
  No complete ATS or FAS scenario implementation is claimed for this file. Partial assertions, if present,
  remain evidence rather than implements links.
partial_scenario_evidence:
  - scenario: ATS-PFM-TNL-009-01
    references:
      - >-
        services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js#runs
        the participant for the tenant and says what it did
      - >-
        services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js#reaches
        a participant of another macroservice through its lifecycle function
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
  - scenario: ATS-PFM-TNL-009-02
    references:
      - >-
        services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js#refuses
        a tenant whose deletion is pending
      - >-
        services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js#refuses
        a tenant that is being deleted
      - >-
        services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js#refuses
        a participant that is not in the registry, and names the ones that are
      - >-
        services-platform:modules/tenants/tests/integration/services/provisioning/initialize-tenant.integration.spec.js#does
        not touch the tenant it refused
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
---
# Platform existing-workspace initialization

## Verification Boundary

The suite invokes production lifecycle services or persistence against its test database. Each fixture and directly called participant belongs to the repository named in the register; this is a local integration boundary.

## What This Suite Proves

Existing-workspace initialization is the inspected subject. The inspected engineering checks remain available in the register. Some may contribute partial assertions to capability scenarios, but the file is not claimed to implement any complete scenario; the unbound inventory records that remaining mapping work.

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