Rhythm 2.0 Specifications

Appearance

WF-PFM-MTD-010Deliver committed business events

Markdown

WF-PFM-MTD-010

Deliver committed business events

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-MTD-015

KindWorkflowProduct areaPlatformModuleMetadata and Organization-defined RecordsRevision1

Read atservices-platform ad3f6a65

Deliver committed business events ​

What It Does ​

The event pipeline separates a committed fact from asynchronous delivery. The outbox retains failed send work; the queue retries individual destination failures.

The Flow ​

When Something Fails ​

A failed or rolled-back mutation leaves no event. Mutation and event fact cannot commit separately. A failed nudge does not fail the saved mutation. The event waits for a later successful schedule. Failed queue sends retain claimed work until it becomes claimable again. Facts remain in the ledger, but destination-free work has no automatic later replay. Queue retries persist through the configured five-receive limit, then dead-letter the message. A persistently failed message remains undelivered even while its fact is retained.

Open Design Questions ​

Replay to a destination registered after publication requires a decision.

Controls

30 controls apply, from the corpus control catalogue.

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

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