Keep AI Objects Outside Custom-Field Registration

Context

The architecture makes custom fields an explicit entity designation rather than a default feature.

Decision

Retain no custom-field capability for this module’s objects unless Andrew separately designates one.

Alternatives Considered

Enable customer-defined fields on AI records: No recorded designation authorizes that capability.

Consequences

There is no LLM object metadata registration declaring custom fields. The existing screens use purpose-built components; future layout decisions still require their own scope.