Remove declared workspace resources and verify the result
Purpose
The purge removes planned participant resources and requires zero inventory before completing deletion.
How It Works
The purge begins by requesting cached-authority invalidation. It then asks each planned participant to remove a batch in reverse construction order. Every Platform batch checks the request’s current purge ownership and workspace state. A participant that needs more work is called again. A blocked result fails with the participant’s explanation. Removal totals are recorded after the participant returns and therefore have a separate failure boundary. Verification inventories planned resources and repeats removal when counts remain. The workspace row is removed at finalization, with conditional customer removal and retained deletion evidence. Failed purges can be retried by authorized staff. Missing remote declarations and Websites’ unpurged CMS resources limit what this verification establishes.
Relationships
- Revalidate the irreversible deletion decision: Its result establishes the state or declared resources needed by this operation.
- Account for each application’s lifecycle responsibilities: Its result establishes the state or declared resources needed by this operation.
- Retain deletion evidence and prevent identifier reuse: Retired identifiers and retained removal history also constrain this work.
- Keep deletion decisions visible to staff: The capabilities share the workspace’s recorded lifecycle decision.
- Recover an incorrect initial import: Its reset classification distinguishes imported records from retained setup.