Rhythm 2.0 Specifications

Appearance

WF-MBR-MEM-010Carry affiliations through a unit merge

Markdown

WF-MBR-MEM-010

Carry affiliations through a unit merge

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-MBR-MEM-008

KindWorkflowProduct areaMembershipModuleMemberships, Applications and Membership BillingRevision1

Read atservices-membership 5994c270react-console baf6dae3

Carry affiliations through a unit merge ​

What It Does ​

A Structure unit merge calls Membership to preserve member connections. The plan chooses transfers, future re-pointings, overlap closures and identity-unit moves before committing the merge.

The Flow ​

When Something Fails ​

An invalid plan rejects the merge before writes, and later failures roll back all effects. Successful merges can lose primary designation. Only the transfer branch publishes separate affiliation events.

Open Design Questions ​

Decide preservation of primary designation and whether every merge branch needs a partner event.

Controls

46 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-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-LOG-005 TC-MON-001 TC-MON-002 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

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