---
id: ADR-PFM-DJE-015
title: No custom fields on engine-owned objects
product_area: platform
module: data-job-engine
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  The module’s jobs, uploads, mappings, runs and capacity records do not
  register custom-field capability; domain jobs may change custom fields only
  through the record owner.
constrains:
  - DOM-PFM-DJE-001
  - DOM-PFM-DJE-003
  - DOM-PFM-DJE-004
  - DOM-PFM-DJE-005
  - DOM-PFM-DJE-006
  - RESP-PFM
origin: >-
  services-platform:docs/standards/custom-field-capability.md (R2-ARCH-001 v1.0,
  approved 2026-10-19) §1 rule 1
alternatives:
  - option: Add administrator-defined fields to engine records
    why_not: >-
      The cited capability standard requires explicit designation, and these
      objects have no such registration.
consequences:
  - Engine objects use purpose-built screens.
  - A contact custom-field update remains a contact save and capability.
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a65: docs/standards/custom-field-capability.md §1,
    §2
---

# No Custom Fields On Engine-Owned Objects

## Context

Custom fields are an explicit capability of an eligible domain entity.

## Decision and Origin

The module’s jobs, uploads, mappings, runs and capacity records do not register custom-field capability; domain jobs may change custom fields only through the record owner. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

## Alternative Comparison

Add administrator-defined fields to engine records: The cited capability standard requires explicit designation, and these objects have no such registration.

## Consequences

Engine objects use purpose-built screens.

A contact custom-field update remains a contact save and capability.