Apply Custom-Field Opt-In to Units

Context

Associations need customer-defined information on units. The recorded standard specifies which entities can opt in and how values are governed.

Decision

This record applies the existing unit designation. Its metadata registration declares shared custom fields and separate configurable form and layout capabilities without implying those screens already exist.

Alternatives Considered

Enable custom fields on additional configuration records. No cited designation authorizes those entities; extending capability requires Andrew's decision. Store unit extras through a bespoke field mechanism. The cited standard requires the shared definition and value-storage mechanism for designated entities.

Consequences

Single-unit and query reads expose custom values, while ordinary lists and tree reads omit them. Custom fields, configurable forms and page layouts are distinct registration capabilities; this record does not decide a future screen layout. Adding a designated entity requires a product record and corresponding metadata opt-in.