Separate Configuration From Member Holdings

Context

The product-area split separates association structure and offers from high-volume member records. Both modules share the deployment and schema, so ownership is an in-process boundary.

Decision

Memberships owns holdings, periods, connections, requests, renewal work and evidence, while Structure supplies referenced configuration and the period engine.

Alternatives Considered

One Membership module owning structure and holdings: Combining the boundaries would mix reusable offer configuration with each member’s changing coverage.

Copy program and package settings onto each term: Duplicated settings would require reconciliation whenever the authoritative configuration changes.

Consequences

Membership writers read the current configuration through its owning module. Structural operations call the holdings owner when they must move member connections. A pure period engine can be extracted for another domain without moving member ownership.