---
id: ADR-PFM-CSH-014
title: Presentation Objects Declare No Custom Fields
product_area: platform
module: console-shell
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Keep custom fields absent from client presentation objects unless Andrew
  designates a capability and an owning registration is introduced.
constrains:
  - DOM-PFM-CSH-001
  - DOM-PFM-CSH-002
  - DOM-PFM-CSH-003
  - DOM-PFM-CSH-004
origin: >-
  services-platform:docs/standards/custom-field-capability.md#2. Classification
  (R2-ARCH-001; Andrew, 2026-10-19: every other app has none until designated)
alternatives:
  - option: Let administrators add fields to menu entries or applications
    why_not: >-
      Field capability on presentation objects requires a separate Andrew
      designation.
consequences:
  - Shell interfaces remain purpose-built from shared components.
  - A placement is a record-type destination rather than a menu custom field.
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a6: docs/standards/custom-field-capability.md §1,
    §2, §5
---
# Presentation Objects Declare No Custom Fields

## Context

The designated-entity standard makes custom fields an explicit registration capability. These objects describe client presentation and have no metadata registrations.

## Decision

Keep custom fields absent for shell objects. A placement links to a customer record type; it does not add fields to the navigation object.

## Alternatives Considered

Configurable fields on menu or application presentation would require a separate product designation.

## Consequences

Shell screens remain purpose-built. Any future field capability needs the recorded designation and registration changes required by the existing standard.