Rhythm 2.0 Specifications

Appearance

SVC-MBR-STR-structureOrganizational Structure Service

Markdown

SVC-MBR-STR-structure

Organizational Structure Service

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaMembershipModuleOrganizational Structure, Membership Configuration and TermsRevision1

Read atservices-membership 5994c270react-console baf6dae3

Organizational Structure Service ​

What This Service Is For ​

Structure holds the association's units, permitted arrangements, dated parentage, organization links and local dues configuration. It supplies the map used by membership visibility and connected readers.

Boundary ​

The service owns hierarchy and unit facets, while Memberships owns member records and affiliations. Merge planning and deletion counts call Memberships inside the local transaction. Accounting, CRM, Commerce, Committees and Platform retain ownership of the records and infrastructure referenced at those boundaries.

Operations in Words ​

Staff define kinds, create units, replace details, move branches, merge sources, close units and delete unused records. Readers can browse or search current records and inspect dated parentage. Link and financial operations maintain local context, and dues operations extend Accounting products without owning their shared fields. Internal ancestry functions and query declarations are listed separately from the HTTP route operations.

Events and Jobs ​

Moves and relocated children publish reparenting before commit. Creation, moves and merges additionally call telemetry after commit; closure and deletion contain no explicit telemetry call in their examined functions. Lifecycle participation supplies provisioning, inventory, batched export and removal, while development setup uses ordinary services.

Consistency Guarantees ​

Placement transactions rebuild derived ancestry before committing. Closure and deletion use narrower writes, and bulk loading explicitly defers rebuilding. Merge atomicity covers the local structural and membership plan; product changes and subscriber effects remain separate consistency boundaries.

Owns
DOM-MBR-STR-001DOM-MBR-STR-002
Repository
services-membership

Controls

49 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-002 TC-DAT-003 TC-DAT-004 TC-DAT-005 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-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 TC-TEN-004

Does Not Own

  • Affiliations, identity-bound memberships and applications referencing units belong to the memberships module.
  • Accounting product identities, prices and status belong to Accounting.
  • CRM organization identities belong to CRM.
  • Ordering profiles belong to Commerce.
  • Committee attachments belong to Committees.
  • Custom-field definitions and registered query infrastructure belong to Platform metadata and Platform query services.
  • Bulk execution and lifecycle coordination belong to Platform import execution and Platform workspace lifecycle coordination.

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