---
id: ADR-PFM-ELG-019
title: No record of this module carries custom fields
product_area: platform
module: eligibility
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Declare no custom-field capability on eligibility, responsibility or attention
  records; rules can still inspect supported fields on evaluated records.
constrains:
  - DOM-PFM-ELG-001
  - DOM-PFM-ELG-002
  - DOM-PFM-ELG-003
  - DOM-PFM-ELG-004
  - DOM-PFM-ELG-005
  - RESP-PFM
origin: >-
  R2-ARCH-001 v1.0 (custom fields are opt-in per entity; every other application
  none until Andrew designates one), approved by Andrew 2026-10-19
alternatives:
  - option: Add custom fields to these infrastructure records
    why_not: The planning layer contains no designation authorizing those entities.
consequences:
  - These screens use their purpose-built contracts.
  - >-
    Validation checks subject custom-field references against workspace
    metadata.
  - Adding configurable forms requires a separate product decision.
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a6: docs/standards/custom-field-capability.md §1,
    §2
---
# No record of this module carries custom fields

## Context

Custom fields require an explicit entity capability and a product designation.

## Decision

Declare no custom-field capability on eligibility, responsibility or attention records; rules can still inspect supported fields on evaluated records.

## Alternatives Considered

Add custom fields to these infrastructure records: The planning layer contains no designation authorizing those entities.

## Consequences

These screens use their purpose-built contracts. Validation checks subject custom-field references against workspace metadata. Adding configurable forms requires a separate product decision.