Purge Meeting and Governance Records
What It Does
Platform resets or deletes a workspace through Committees lifecycle participants. The participant boundary differs from design ownership: openings are declared under committees, and the shared event ledger under meetings. Database rows are purged in batches; this source does not establish remote coordinator behavior or removal of stored file objects.
The Flow
Purge meetings-owned working tables in their declared local order, including event delivery, room and notice work, materials, links, agenda, participants, meetings, series and asset lifecycle rows. Purge decisions-owned and minutes-owned participants before their meeting parents; protected governance records and versions use the declared definer purge function. Purge openings and interests through the committees participant that declares them.
When Something Fails
Roll back a failed batch and retry it. The workspace remains partially purged until completion. Retry a failed table batch. Earlier successful batches remain deleted. Retry the failed batch. Recruitment data can remain until that participant completes.
Open Design Questions
The participant boundary differs from design ownership: openings are declared under committees, and the shared event ledger under meetings. Database rows are purged in batches; this source does not establish remote coordinator behavior or removal of stored file objects.