--- id: CON-MBR-STR-004 name: Membership Package feature: FEAT-MBR-STR-04 product_area: membership module: structure revision: 1 status: draft product_intent: proposed implementation_evidence: observed source_sha: services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f definition: >- A membership package adds membership-specific terms and entitlements to an Accounting product, using the same product identity. owned_by: MOD-MBR-STR synonyms: - membership offering - package not_to_be_confused_with: - Membership type - Chapter dues product - Commerce order facets: - name: Shared product meaning: 'Accounting supplies the offering’s identity, name, description, status, visibility and prices.' used_for: Presenting and selling one product across application concerns. - name: Membership context meaning: A program and its classification describe the holding a purchase grants. used_for: Selecting the membership created by the offering. - name: Date rule meaning: 'Anniversary, calendar and never-ending choices describe the period granted.' used_for: Computing term dates with optional fixed windows. - name: Renewal behavior meaning: 'Windows, continuation, default renewal target and reinstatement settings describe later purchases.' used_for: Supplying renewal eligibility and period inputs. - name: Commerce and seats meaning: Pricing audience and proration hints accompany the organizational seat allowance. used_for: Supplying consumer inputs without computing prices. - name: Additional holdings meaning: Grants describe memberships in other programs accompanying the offering. used_for: Building membership bundles. - name: Affiliation specialization meaning: Package counts and dues choices specialize program unit requirements. used_for: Describing offering-specific affiliation needs. - name: Change policy meaning: A referenced policy set records intended upgrade and downgrade treatment. used_for: Preparing future change processing. relationships: - to: CON-MBR-STR-003 statement: The package’s classification belongs to its selected program. provenance: observed source: 'services-membership:modules/configuration/db/membership-packages.table.ts:membershipPackages' - to: CON-MBR-STR-005 statement: The extension’s rule supplies inputs for term-date calculation. provenance: observed source: 'services-membership:modules/configuration/services/persistence/membership-packages.ts' - to: CON-MBR-STR-002 statement: Local dues extensions can identify a package-specific context. provenance: observed source: >- services-membership:modules/structure/db/organizational-unit-dues-products.table.ts:organizationalUnitDuesProducts lifecycle: - state: active meaning: Accounting currently reports the product active. how_it_changes: Changes to Accounting product availability change the extension’s returned activity. - state: inactive meaning: 'The backing product is inactive, retired or unavailable.' how_it_changes: Changes to Accounting product availability change the extension’s returned activity. acted_on_by: - CAP-MBR-STR-008 - CAP-MBR-STR-012 - CAP-MBR-STR-013 - CAP-MBR-STR-014 - CAP-MBR-STR-015 - CAP-MBR-STR-018 visible_to: - ACT-MBR-001 - ACT-MBR-002 - ACT-MBR-003 - ACT-MBR-005 evidence: - >- services-membership: Verified material includes packages, fixed term ends, grants, unit rules and change policy tables, schemas and persistence; the Accounting products port. - >- services-membership: Verified material includes packages-as-products and database refusals end-to-end; configuration acceptance journeys. supersedes: - react-console acceptance inventory CAP-MBR-CFG-004 - react-console acceptance inventory CAP-MBR-CFG-006 - react-console acceptance inventory CAP-MBR-CFG-007 - react-console acceptance inventory CAP-MBR-CFG-009 --- # Membership Package ## What It Is A membership package is the offering members recognize when purchasing membership, such as Regular Annual or a lifetime option. It uses the identity of an Accounting product rather than maintaining another independently named sellable record. Staff save that product first, then add its Membership extension. Accounting continues to supply shared catalogue information, including the product’s name, status, visibility and prices. Membership adds the information particular to the entitlement: its program and classification, term rule, renewal choices, organizational seat allowance and optional grants or unit requirements. Reading the package combines the extension with current product information. Changes to the shared product therefore appear without copying those fields into Membership. The extension can be removed without removing the product itself. ## What It Is Not A package is distinct from a membership type. The type classifies the granted membership; the package describes an offering that grants it. Local dues are another product type associated with a unit. An order belongs to Commerce and can include the membership package alongside other lines. The package configuration does not itself prove payment or fulfilment. ## How It Is Used Administrators prepare several offerings for a program and adjust renewal settings as policy develops. Commerce and membership operations read those choices for their respective work. Staff should inspect both the extension and its product when availability is surprising. An active product does not settle every owner or membership eligibility condition. Removing the extension is also different from retiring the shared product. Readers of activity-filtered lists must follow continuation even when a returned page has no matching offerings. ## Its Facets **Shared product.** One identity prevents competing names and status fields. **Membership context.** The selected classification belongs to the selected program. **Date rule.** Length and calendar choices determine the period rather than its monetary price. **Renewal behavior.** Continuation and reinstatement distinguish different later purchases. **Commerce and seats.** Consumer hints accompany the organizational membership’s capacity setting. **Additional holdings.** Grants describe bundled program memberships and their date choices. **Affiliation specialization.** Package-specific counts and dues can override program defaults. **Change policy.** Stored cases describe future upgrade and downgrade work that remains unavailable. ## How It Relates Programs and classifications give the package its membership context. The term lifecycle computes dates from its rule. Organizational units can offer package-specific dues products beside the package. Accounting owns the common product, while Commerce owns selling and monetary interpretation. The memberships module owns resulting holdings, terms and affiliations. ## What It Could Become The product should settle empty reinstatement semantics before migrated packages rely on them. It should also decide the presentation of packages prepared on inactive products and the compatibility checks required for grants. Future change processing needs validated policy references and a clear matching model. Those decisions can make the existing configuration usable without implying that every retained setting already changes behavior.