Activities and tasks carry no custom fields

Context

The architecture makes custom fields an entity capability chosen explicitly. The earlier interaction implementation lost that capability under the cited ruling.

Decision

The registrations omit custom-field support, and the API schemas reject those values. This record cites the existing architecture decision rather than granting a new opt-in.

Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

Consequences

Forms and integrations use the current defined fields. Additional bespoke data requires a new decision and capability declaration.