---
id: ADR-PFM-OPS-015
title: The module’s records carry no custom fields
product_area: platform
module: operations
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
decision: 'Keep jobs, activity events, licences and operational application records outside custom-field configuration.'
constrains:
  - DOM-PFM-OPS-001
  - DOM-PFM-OPS-002
  - DOM-PFM-OPS-003
  - DOM-PFM-OPS-004
origin: >-
  services-platform:docs/standards/custom-field-capability.md (R2-ARCH-001 v1.0, approved by Andrew
  2026-10-19: custom fields are opt-in per entity)
alternatives:
  - option: Custom fields on operational jobs or licences
    why_not: The examined registrations provide no consumers for customer-defined values on these records.
consequences:
  - These records have no configurable customer capture layout.
  - Any future opt-in requires a deliberate registration change.
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a6: docs/standards/custom-field-capability.md; modules/jobs, modules/audit,
    modules/licensing (no custom-field declaration).
  - >-
    codex examination 2026-10-23: checked the pinned source anchors, planning references and enforcement
    boundaries; unresolved limits are recorded in module findings.
---

# The module’s records carry no custom fields

## Context

Custom-field support is an explicit capability rather than a property of every stored record.

## Decision

Retain the existing fixed-shape operational records without a custom-field declaration.

## Alternatives Considered

Adding customer fields would introduce configuration with no implemented consumer.

## Consequences

The design describes only the attributes and facets these services currently handle.