Rhythm 2.0 Specifications

Appearance

WF-ACC-BKS-010Purge Workspace Accounting Records in Batches

Markdown

WF-ACC-BKS-010

Purge Workspace Accounting Records in Batches

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-ACC-BKS-019

KindWorkflowProduct areaAccountingModuleBooks, Business Units and Chart of AccountsRevision1

Read atservices-accounting f47cb263

Purge Workspace Accounting Records in Batches ​

What It Does ​

Purge removes the selected workspace’s Accounting records through small resumable calls. Participant dependencies and local child-first orders keep referenced configuration until dependent work is removed. Platform owns the continuing loop; Accounting performs a bounded step and reports its result.

The Flow ​

When Something Fails ​

A failed batch rolls back itself. Later calls rediscover progress from remaining rows, so no cursor restoration is required. Each batch checks current deleting standing without the availability cache. If that standing changes after partial erasure, subsequent calls stop, while earlier deletion remains permanent. Declaration and purge-order tests check coverage against database references; bindings alone do not establish a production execution.

Open Design Questions ​

The configuration participant still declares records owned by Products and Batches. The ownership of those lifecycle declarations needs to be considered alongside each module’s own dataset and reader declarations.

Controls

24 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-DAT-001 TC-DAT-004 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software