Only Contacts and Organizations Carry Custom Fields

Context

The approved custom-field standard determines ownership, and the pinned registrations match it. Contacts and organizations explicitly advertise their presentation and custom-value capabilities.

Decision

Contact and organization registrations enable custom fields, configurable forms and page layouts; affiliations, roles and classification catalogues declare no custom-field capability and reject custom-value payloads.

Alternatives Considered

Extend custom fields to affiliations or roles. The approved capability standard excludes them unless Andrew designates an additional owner.

Create a bespoke CRM custom-value mechanism. The standard requires shared definitions and value storage instead of an entity-specific parallel system.

Consequences

Catalogue and relationship models remain facets without their own custom-value storage. Further extensibility must follow an explicit designation rather than arise from adding an undocumented payload property.

Person and organization presentation uses shared form and layout capabilities; catalogue editing uses configuration resources. Affiliation, role and classification writes reject an unknown custom-value property.