---
id: ADR-PFM-LLM-015
title: Keep AI Objects Outside Custom-Field Registration
product_area: platform
module: llm
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: Retain no custom-field capability for this module’s objects unless Andrew separately designates one.
constrains:
  - DOM-PFM-LLM-001
  - DOM-PFM-LLM-002
  - DOM-PFM-LLM-003
  - DOM-PFM-LLM-004
  - DOM-PFM-LLM-005
  - SVC-PFM-LLM-llm
  - SVC-PFM-LLM-console-agent
origin: >-
  R2-ARCH-001, Custom Fields Are Opt-In Per Entity, section 2 classification (Andrew, 2026-10-19): every other
  application has none until Andrew designates one
  (services-platform:docs/standards/custom-field-capability.md#2. Classification (Andrew, 2026-10-19)).
alternatives:
  - option: Enable customer-defined fields on AI records
    why_not: No recorded designation authorizes that capability.
consequences:
  - There is no LLM object metadata registration declaring custom fields.
  - The existing screens use purpose-built components; future layout decisions still require their own scope.
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a6: docs/standards/custom-field-capability.md; modules/llm has no metadata
    registration.
---

# Keep AI Objects Outside Custom-Field Registration

## Context

The architecture makes custom fields an explicit entity designation rather than a default feature.

## Decision

Retain no custom-field capability for this module’s objects unless Andrew separately designates one.

## Alternatives Considered

Enable customer-defined fields on AI records: No recorded designation authorizes that capability.

## Consequences

There is no LLM object metadata registration declaring custom fields. The existing screens use purpose-built components; future layout decisions still require their own scope.