No custom-field capability

Context

The custom-field classification already governs these records. The implementation has no enabling registration in this module; the examination does not invent a capability declaration.

A future designation must follow the existing product-decision and registration process.

Decision

Retain the approved default of no custom fields for customer, workspace and security records; no enabling object registration is present and their screens use dedicated shared components.

Alternatives Considered

Enable custom fields for commercial or workspace attributes. The existing classification does not designate these records, so enabling them requires Andrew’s separate product decision.

Consequences

Absence of a custom-field enabling declaration means the capability is off under the cited standard.

The observed screens are dedicated components rather than registered configurable forms or page layouts.