Rhythm 2.0 Specifications

Appearance

SVC-MBR-STR-configurationMembership Configuration Service

Markdown

SVC-MBR-STR-configuration

Membership Configuration Service

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaMembershipModuleOrganizational Structure, Membership Configuration and TermsRevision1

Read atservices-membership 5994c270react-console baf6dae3

Membership Configuration Service ​

What This Service Is For ​

Configuration describes the association's programs, classifications, sellable membership effects, status explanations and stored change policies. It supplies common identity, version and list-save handling to those records.

Boundary ​

The service owns configuration records and owned lists. Memberships owns the holdings they shape, application process definitions and content history. Accounting supplies shared product identity and activity, Commerce resolves ordering and pricing context, and CRM owns the references selected for flow-down.

Operations in Words ​

Program administrators maintain program records and replace affiliation requirements. Configuration administrators maintain types and flow-down, package extensions and grants, reasons and policy sets. Lists use identifier order and declared filters, including either activity value. Updates retain omitted content, and removal checks the required version and protected references.

Events and Jobs ​

The configuration streams capture content history transactionally and do not publish an external business event. Programs, types and packages have bulk declarations; status reasons, policy sets and program requirements do not. Lifecycle exports describe all configuration datasets, and development seeding supplies known records.

Consistency Guarantees ​

Each record save includes submitted lists and history settlement in one transaction. The documented product-first setup retains a weaker boundary with Accounting because no caller composes an atomic offering save. Live settings can change existing membership computations, while requirement removal retains a gap with concurrent affiliation additions.

Owns
DOM-MBR-STR-003DOM-MBR-STR-004DOM-MBR-STR-006
Repository
services-membership

Controls

42 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-005 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-004 TC-DAT-007 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 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-SEC-001 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003

Does Not Own

  • Application process definitions belong to the memberships module despite sharing the configuration store.
  • Configuration content history belongs to the memberships module history streams.
  • Lifecycle execution and configuration export coordination use the the memberships module participant with Platform workspace lifecycle coordination.
  • Shared Accounting products and prices belong to Accounting.
  • Ordering profiles and pricing audiences belong to Commerce and MOD-COM-CAT.
  • Flow-down's CRM roles and organization types belong to CRM.
  • Bulk job execution belongs to Platform import execution.

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