Purge a workspace’s transactions
What It Does
Lifecycle purge removes the module’s retained financial data in dependency order. A failed batch can leave deletion partially complete until lifecycle retry.
The Flow
The numbered hops identify the participating services, synchronization boundary and evidence. Branch conditions in the frontmatter explain where preparation, completion and recovery diverge.
When Something Fails
Each hop records its rollback, retry or compensation boundary and the result visible to callers or operators. External outcomes can remain unresolved after local preparation commits; the listed recovery behavior defines what remains pending.
Open Design Questions
Verify Platform-wide writer exclusion during deletion; the local participant establishes deletion state rather than that complete concurrency guarantee.