Membership Responsibilities
How the Product Area Is Divided
Organizational structure, configuration and terms owns association setup and the calculations that interpret membership dates and standing. Memberships, applications and membership billing owns member-specific records and the processes that apply those calculations. The latter module has no design responsibility row yet.
Organizational Structure, Configuration and Terms
The ownership, exposed operations and invariant references above define this module's boundary. Structure arranges units and retains their dated parentage; configuration defines programs, membership types, packages and reasons; the term engine calculates periods and standing from supplied inputs. Consumers remain responsible for recording member-specific results. The contracts distinguish operations that require a version from those with optional or absent checks, and placement transactions from imports that need a separate ancestry rebuild.
Memberships, Applications and Membership Billing
The module owns six broad objects: membership, term, unit affiliation, typed application, renewal batch and history. Its service contracts divide implementation among holdings, application handling, renewal billing, checkout participation, timelines, reporting and event delivery. The exposure list records actual route operations and named internal entry points, including deployment health; the event list includes the shared delivery of Structure’s unit movement event. Detailed invariants and enforcement limits remain with the object and service contracts.
The module can describe its local database boundaries, but those boundaries do not establish complete live partner journeys. Default ordering, contact-update and decision-acknowledgement adapters refuse. Intake, subscriptions, portal-role wiring and job recovery retain the gaps already recorded by examination.
What Is Delegated to Platform and Other Areas
Platform provides metadata, authorization, query and export facilities, workspace lifecycle coordination and import execution. Accounting supplies the products extended by packages and dues offerings; Commerce supplies ordering and settlement; CRM supplies the referenced organizations and roles; Committees retains committee records. The memberships module performs scheduled standing updates and provides configuration revision history through the shared capture mechanism. Business-event delivery uses the macroservice dispatcher after commit, with delivery guarantees limited to the evidence described in the workflows.