Declare Custom Fields Through Shared Metadata

Context

The custom-field standard selects participating entities through registration. Existing Membership storage must be read alongside that declaration.

Decision

Membership registration enables shared custom fields; other module records have no declared value capability, including the currently unregistered application.

Alternatives Considered

An entity-specific custom field mechanism: A module-specific mechanism would conflict with the shared capability requirement.

Custom fields on terms or affiliations: Adding term or affiliation fields would require an explicit entity selection by Product.

Consequences

Membership values have storage and evidence but no available staff or import write path. The application declaration gap conflicts with the standard’s named entity list. Reporting can reconstruct stored membership custom values as characteristics.