Skip to content

CON-MBR-MEM-003Unit Affiliation

Markdown

CON-MBR-MEM-003

Unit Affiliation

Markdown
  • DocumentDraft
  • Product intentConfirmed
  • ImplementationObserved

Planning

Feature
FEAT-MBR-MEM-02
Owned by
MOD-MBR-MEM
Acted on by
CAP-MBR-MEM-007, CAP-MBR-MEM-008, CAP-MBR-MEM-009, CAP-MBR-MEM-015, CAP-MBR-MEM-016
Visible to
ACT-MBR-006, ACT-MBR-007, ACT-MBR-008, ACT-MBR-009, ACT-MBR-010
Not to be confused with
CRM affiliations connect people to organizations., An identity-bound chapter program establishes a separate membership holding., The structure module owns the unit and its place in the hierarchy.

Design

Specified by
DOM-MBR-MEM-003

KindKey conceptProduct areaMembershipModuleMemberships, Applications and Membership BillingRevision1

Read atservices-membership 5994c270react-console baf6dae3

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Definition
A unit affiliation connects a membership term to a chapter, section or another organizational unit for a dated span, retaining its primary designation, origin and any purchased dues reference.
Synonyms
chapter affiliationchapter membership (informally)

Relationships

ToStatementProvenance
CON-MBR-MEM-002The membership term owns the connection and bounds its effective dates.observed
CON-MBR-MEM-001Effective affiliations and their unit ancestors contribute to the membership visibility chain used for officer access.observed

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.