The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | patchHqTenant | Disable the departing customer’s workspace. | CAP-PFM-TNL-006 | Ordinary customer access closes. | test services-platform:modules/tenants/tests/e2e/tenant-deletion-requests.e2e.spec.js#lets Rhythm staff change the same status |
| 2 | requestTenantDeletion | Confirm its exact name and record the deletion reason. | CAP-PFM-TNL-013 | The standard request fixes a waiting date and pending-deletion lifecycle. | test services-platform:modules/tenants/tests/e2e/tenant-deletion-requests.e2e.spec.js#answers a scheduled request against the tenant asked about |
| 3 | tenant_deletion_schedule: notices | Send the initial internal deletion notice. | CAP-PFM-TNL-015 | The request notice reaches the staff list and requester. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-deletion-schedule.integration.spec.js#sends the requested notice on the day of the request |
| 4 | holdTenantDeletionRequest, releaseTenantDeletionRequest | Hold for export questions and release after resolution. | CAP-PFM-TNL-014 | The recorded pause and release preserve review time and reminder obligations. | test services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#pushes the date out three days when the original is nearly here |
| 5 | tenant_deletion_schedule: notices | Deliver the scheduled waiting-period reminders. | CAP-PFM-TNL-015 | The reminders occur at their due instants. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-deletion-schedule.integration.spec.js#sends both reminders, each on its own day, as the waiting period passes |
| 6 | tenant_deletion_schedule: begin-destruction | Recheck current guards at eligibility. | CAP-PFM-TNL-016 | Executing state, deleting lifecycle and the purge job are recorded together. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-deletion-schedule.integration.spec.js#begins destruction at the end of the period, and the request records it |
| 7 | getHqTenant | Read the workspace details through HQ during removal. | CAP-PFM-TNL-005 | The workspace details remain available to authorized staff. | observed services-platform:modules/tenants/aws/api/tenants.routes.ts:getTenantForStaff |
| 8 | tenant_purge | Drive planned participant batches and inventories. | CAP-PFM-TNL-017 | The tested purge completes its declared removal and verification. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#runs the purge to the end and succeeds |
| 9 | getTenantDeletionRequest | Inspect the retained completed deletion decision. | CAP-PFM-TNL-018 | Removal totals, verification and completed ledger work remain recorded. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#records on the request what was removed, and the counts it verified |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 4 | The customer returns before execution. | Cancel the scheduled removal. | The workspace becomes active but needs separate staff re-enablement. | test services-platform:modules/tenants/tests/integration/services/deletion/deletion-holds.integration.spec.js#leaves the tenant disabled: calling off a deletion restores nobody access |
| failure | 5 | A required reminder fails delivery. | Keep the schedule waiting for its gating notice. | Destruction does not start with failed required delivery. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-deletion-schedule.integration.spec.js#holds the deletion indefinitely when a notice could not be delivered, rather than destroying the tenant unannounced |
| failure | 8 | A participant cannot remove its resource. | Record the blocked failure, correct its cause and request retry. | The replacement purge finishes the fixture’s remaining work. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-recovery.integration.spec.js#completes the destruction when a purge that failed part way is retried |
| failure | 6 | The requester loses staff deletion authority. | Hold the request with an authority explanation. | A person must review before destruction proceeds. | test services-platform:modules/tenants/tests/integration/services/deletion/begin-destruction.integration.spec.js#holds the request in that case, so a person has to look at it rather than a job retrying forever |
| Id | Statement | Provenance |
|---|---|---|
01 | The tested declared Platform and CRM tables retain no removed-workspace rows after purge. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#leaves no row of the tenant in any table a participant declares |
02 | The sibling workspace fixture remains unchanged. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#leaves the other tenant of the same customer exactly as it was |
03 | Cancellation that wins before destruction preserves the records; a later cancellation refuses. | test services-platform:modules/tenants/tests/integration/services/deletion/begin-destruction.integration.spec.js#lets exactly one of the two win, every round |
04 | The completed fixture retains numeric evidence and refuses reuse of the retired identifier. | test services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-recovery.integration.spec.js#refuses to create a tenant again under the id of one that was deleted |
End-to-end policy: required: The outcome crosses lifecycle operations and warrants end-to-end verification; the current bindings establish backend fixtures, while screen and deployed-service coverage remain separate gaps.