Share Accounting Identity for Membership Offerings

Context

The former package model stored its own name and activity alongside a separate product. The recorded change establishes one shared product identity with a Membership extension.

Decision

This record documents the existing product decision. Membership owns membership-specific configuration, while Accounting retains the product and its shared fields.

Alternatives Considered

Maintain an independently named package pointing to an arbitrary product. Separate descriptions and activity could drift for what staff regard as one offering; the recorded product decision replaces this model. Transfer the entire product catalogue record to Membership. That would move shared pricing and Accounting responsibilities across their established service boundary.

Consequences

Accounting and Membership reference the same offering identity and Accounting status. Package and dues reads obtain shared product fields through one port. Product references are soft and validated on extension creation; later package updates do not repeat that validation.