---
id: TST-PFM-TNL-062
title: 'Platform hold, release and cancellation'
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/deletion/deletion-holds.integration.spec.js
implements:
  - ATS-PFM-TNL-014-03
  - ATS-PFM-TNL-014-04
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/deletion/deletion-holds.integration.spec.js'
  - >-
    services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js
    imports ../../../../services/deletion/deletion-holds
  - >-
    services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js
    imports ../../../../services/deletion/request-deletion
  - >-
    services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js
    imports ../../../../services/persistence/tenant-deletion-requests
  - >-
    services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js
    imports ../../../../services/persistence/tenants
  - >-
    services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js
    imports ../../../../services/lifecycle/lifecycle-refusals
  - >-
    services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js
    imports ../../support
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-014-01
    references:
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#refuses
        a caller who is not Rhythm staff
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
  - scenario: ATS-PFM-TNL-014-02
    references:
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#refuses
        a hold with no reason worth reading
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#refuses
        a request that has changed since the screen was drawn
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#leaves
        that request scheduled after the stale refusal
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
  - scenario: ATS-PFM-TNL-014-05
    references:
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#answers
        a cancelled request
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#returns
        the tenant to active
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#leaves
        the tenant disabled: calling off a deletion restores nobody access
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#cancels
        a held request too
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
  - scenario: ATS-PFM-TNL-014-06
    references:
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#refuses
        to cancel a request whose destruction has begun
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#leaves
        that executing request exactly as it was
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
  - scenario: ATS-PFM-TNL-015-02
    references:
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#owes
        a notice, because a schedule that changes silently is a schedule nobody can trust
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#owes
        a released notice
      - >-
        services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#owes
        a cancelled notice
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
---
# Platform hold, release and cancellation

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

Hold, release and cancellation 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 suite retains its database and production functions as shown by the cited source. Fixture clocks, contexts, seeded Platform facts or callback dependencies remain test inputs. The imported support is recorded as evidence; no external provider result is inferred from a local fixture.

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