Rhythm 2.0 Specifications

Appearance

SVC-MBR-MEM-eventsMembership Business Events Service Module

Markdown

SVC-MBR-MEM-events

Membership Business Events Service Module

Markdown
  • DocumentDraft
  • ImplementationPartially observed

KindService contractProduct areaMembershipModuleMemberships, Applications and Membership BillingRevision1

Read atservices-membership 5994c270react-console baf6dae3

Membership Business Events Service Module ​

What This Service Is For ​

The event service preserves strict partner messages describing committed membership changes. It delivers configured receiver work through the shared change-event transport.

Boundary ​

Business writers state events; this service owns the publication and dispatch facet of membership history. Receivers own their reactions. The separate integration catalogue remains an unresolved ownership choice.

Operations in Words ​

The in-process publisher requires a transaction and validates payloads before insertion. Dispatcher and consumer functions claim transport work, identify matching handlers and report delivery outcomes.

Events and Jobs ​

Nine event types cover periods, unit connections, suspension and tree movement. The dispatcher runs every minute; matched work reaches the queue and persistent failures reach its dead-letter queue. Without a configured Committees receiver, transport is discarded while the published log remains.

Consistency Guarantees ​

Publication rolls back with its source write. Delivery can repeat and arrive out of order, so receivers require deduplication. A dispatch interval does not establish a delivery deadline or imply that every logged event has a receiver.

Repository
services-membership

Controls

44 controls apply, from the corpus control catalogue.

TC-AVL-002 TC-AVL-003 TC-AVL-004 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-007 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-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 TC-PRV-001 TC-PRV-002 TC-SEC-001 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003

Does Not Own

  • History owns the broad evidence concept; this service implements its publication facet.
  • Committees owns appointment changes resulting from delivered termination.
  • Platform owns the integration catalogue, where these event keys remain unregistered.

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