---
id: ADR-PFM-TNL-014
title: Custom Fields Remain Undeclared
product_area: platform
module: tenant-lifecycle
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: Declare no custom-field capability for lifecycle orchestration records.
constrains:
- DOM-PFM-TNL-001
- DOM-PFM-TNL-002
- DOM-PFM-TNL-003
- DOM-PFM-TNL-004
- DOM-PFM-TNL-005
- SVC-PFM-TNL-tenants
origin: services-platform:docs/standards/custom-field-capability.md#§1, §2 (R2-ARCH-001, Andrew 2026-10-19)
alternatives:
- option: Allow custom fields on deletion requests or provisioning
  why_not: 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.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: docs/standards/custom-field-capability.md.'
---

# 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.