Rhythm 2.0 Specifications

Appearance

SVC-ACC-BKS-maintenanceAccounting scheduling and lifecycle service

Markdown

SVC-ACC-BKS-maintenance

Accounting scheduling and lifecycle service

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaAccountingModuleBooks, Business Units and Chart of AccountsRevision1

Read atservices-accounting f47cb263

Accounting scheduling and lifecycle service ​

What This Service Is For ​

Maintenance times recurring Accounting work and supplies bounded provisioning, export and erasure steps to Platform. It also gates Accounting requests against observed workspace availability.

Boundary ​

Owning modules save their schedule definitions and implement business handlers. Maintenance supplies recurrence, dispatch and history. Platform owns lifecycle transitions and continuation; participant declarations and dataset readers also live beside other Accounting modules.

Operations in Words ​

Staff can preview recurrence without saving and read history only with the owning record’s read permission. Internal lifecycle calls describe participants, provision and verify setup, count remaining rows, purge one batch or export one dataset batch. None is a Submissions intake operation.

Events and Jobs ​

The dispatcher commits before publishing. Explicit publication refusal releases the offered run, but a crash in that gap can strand it. The consumer can repeat unfinished handler work, including concurrent duplicate deliveries. Expected business refusals settle without retry; unexpected errors redeliver, with successful final failure recording acknowledged rather than sent to the dead-letter queue.

Consistency Guarantees ​

Provisioning uses conflict-safe insertion. Purge is bounded, guarded and irreversible after commit. Export checks recognized secret shapes, not every possible secret, and its creation cutoff does not provide a value snapshot. Cache delays affect ordinary availability; purge reads standing afresh. Posting prepared by a scheduled close has a separate post-commit start boundary.

Repository
services-accounting

Controls

52 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-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-DAT-005 TC-DAT-007 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-006 TC-AVL-001 TC-AVL-002 TC-AVL-003 TC-AVL-004 TC-AVL-005 TC-MON-001 TC-MON-002 TC-MON-003 TC-MON-004 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005

Does Not Own

  • Batches, Reconciliation and Billing own the business handlers invoked for their schedules.
  • Platform owns workspace records and the jobs ordering provisioning, export and erasure.
  • Transactions declares its own participant, which maintenance registers.
  • Schedule history and lifecycle facets belong to the Accounting workspace object shared with configuration.

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