No custom-field capability in the examined configuration

Context

The registered business-unit object omits the custom-field capability, and configuration requests use strict schemas. This is an implementation observation rather than approval of a permanent exclusion.

Decision

Books declares no custom-field capability. Unknown request properties are rejected, and department and project requests explicitly refuse custom-field values.

Alternatives Considered

Enable custom fields for units or accounts. A product need and an explicit capability declaration have not been established in the examined sources.

Add a private extension column. The cited standard favors shared definitions and value storage; its full text remains outside this examination.

Consequences

These configuration records do not currently expose Platform custom-field, form or layout features.

Adding customer-defined attributes requires an explicit capability decision and a compatible persistence contract.