Custom Fields Remain Undeclared

Context

These system and staff records use a defined orchestration contract. The examined design does not expose association-defined record properties for them.

Decision

Declare no custom-field capability for lifecycle orchestration records.

Alternatives Considered

Allow custom fields on deletion requests or provisioning: Allowing extensions would need an explicit product capability and supported record design.

Consequences

Lifecycle forms use their specified attributes; this does not by itself prove a console layout restriction. Lifecycle records require no enabled custom-field capability in their own contracts.