---
id: ADR-ACC-CLS-010
title: No Custom-Field Inputs Appear in the Examined Close Boundary
product_area: accounting
module: close
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Close currently has no custom-field inputs or value storage, with strict
  command schemas; record-registration capability declarations remain
  unverified.
constrains:
  - DOM-ACC-CLS-001
  - DOM-ACC-CLS-002
  - DOM-ACC-CLS-003
  - DOM-ACC-CLS-004
  - SVC-ACC-CLS-fiscal-close
origin: >-
  R2-ARCH-001 v1.0 (Andrew, 2026-10-19) §2: custom fields only on the record
  types it designates
alternatives:
  - option: Make customer checklist additions into run custom fields.
    why_not: >-
      The adopted design uses deterministic readiness evaluators, and no
      verified registration establishes custom-field support for close.
consequences:
  - >-
    A proposed customer-specific control needs an explicit readiness design
    rather than an undeclared field.
  - >-
    The current export and purge declarations cover the module’s existing stored
    record groups.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263:
    modules/fiscal-close/aws/api/fiscal-close.schemas.ts (closed request
    schemas); modules/fiscal-close/db/*.table.ts (no custom-value storage).
---

# No Custom-Field Inputs Appear in the Examined Close Boundary

## Context

Custom-field support requires a deliberate record-type capability declaration under the adopted standard, rather than inference from flexible storage.

## Decision

Preserve the no-custom-field design for these close objects. The inspected code supports absence of use; it does not supply the registration declaration needed to independently verify that part of the standard.

## Alternatives Considered

Make customer checklist additions into run custom fields. The adopted design uses deterministic readiness evaluators, and no verified registration establishes custom-field support for close.

## Consequences

A proposed customer-specific control needs an explicit readiness design rather than an undeclared field. The current export and purge declarations cover the module’s existing stored record groups.