---
id: TST-MBR-STR-004
title: 'Structure provisioning, reset and purge'
kind: integration
product_area: membership
module: structure
revision: 1
status: draft
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-membership
files:
  - modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts
implements:
  - ATS-MBR-STR-020-01
  - ATS-MBR-STR-020-02
  - ATS-MBR-STR-020-03
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: A uniquely named local workspace and its seeded records; the suite owns its fixture data and cleanup.
evidence:
  - >-
    services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts
bindings:
  - scenario: ATS-MBR-STR-020-01
    source: >-
      services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts#the
      structure participant in the database › seeds the four relationship types at provisioning
    provenance: test
  - scenario: ATS-MBR-STR-020-01
    source: >-
      services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts#the
      structure participant in the database › writes nothing on a second provisioning
    provenance: test
  - scenario: ATS-MBR-STR-020-01
    source: >-
      services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts#the
      structure participant in the database › reports a provisioned tenant ready
    provenance: test
  - scenario: ATS-MBR-STR-020-02
    source: >-
      services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts#the
      structure participant in the database › refuses to purge a tenant Platform is not deleting, before
      any row is removed
    provenance: test
  - scenario: ATS-MBR-STR-020-02
    source: >-
      services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts#the
      structure participant in the database › refuses to purge a tenant Platform holds no row of, before
      any row is removed
    provenance: test
  - scenario: ATS-MBR-STR-020-02
    source: >-
      services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts#the
      structure participant in the database › purges every table of a tenant being deleted, versions
      included, and leaves another tenant whole
    provenance: test
  - scenario: ATS-MBR-STR-020-03
    source: >-
      services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts#the
      structure participant in the database › refuses to reset the tree of a tenant that is active,
      before any row is removed
    provenance: test
  - scenario: ATS-MBR-STR-020-03
    source: >-
      services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts#the
      structure participant in the database › resets the tree of a tenant being reset and keeps its unit
      and relationship types
    provenance: test
invocation: 'npm run test:integration'
coverage_limit: >-
  Bindings identify the concrete cases executed in this file. A compound specification may also depend on
  other registered suites or remain partly proposed; registration is not a passing execution result.
provenance: test
source:
  - >-
    services-membership:modules/structure/tests/integration/services/lifecycle/structure-participant.integration.spec.ts
---

# Structure provisioning, reset and purge

## Verification Boundary

This suite invokes the local implementation against the prepared database and checks its persisted results. Structure provisioning, reset and purge defines the scope of its examples.

## What This Suite Proves

The suite executes the concrete examples named by its binding ledger. Those examples contribute to the linked capability or feature scenarios within the boundary of the test assertions.

## What It Does Not Prove

Registration supplies no fresh execution result or deployed conformance verdict. Browser behavior, deployed infrastructure and unasserted variants require separate evidence.

## Real Dependencies and Test Doubles

PostgreSQL, local Membership services and the suite’s persistence path are real. The business clock and caller fixtures are controlled by the harness.

## Must Not Be Doubled

The Membership path under examination, transaction behavior and database constraints stay real. Replacing those boundaries would remove the persisted proof the suite is intended to supply.