---
id: ADR-PFM-MTD-006
title: Read-only records under inactive definitions
product_area: platform
module: metadata
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: Ordinary custom-record changes require an active category, while retained records under inactive definitions
  remain readable by identity and removable through applicable cascades.
constrains:
- DOM-PFM-MTD-005
- STATE-PFM-MTD-003
- STATE-PFM-MTD-005
- SVC-PFM-MTD-custom-objects
- SCR-PFM-MTD-016
origin: 'PLAT-M5 D3 (Andrew, 2026-10-19: readable, read-only) and B5 (rule applies anyway), services- platform:docs/milestones/PLAT-M5-custom-records.md#Decisions'
alternatives:
- option: Hiding every inactive-category record
  why_not: References and retained historical navigation would lose their readable targets.
- option: Continuing direct writes after retirement
  why_not: Archival would cease to be an effective boundary for ordinary maintenance.
- option: Stopping cascades at inactive categories
  why_not: Owner deletion could violate the continuing ownership policy and leave dependants behind.
consequences:
- Record writes hold a shared parent lock while checking active status.
- Screens retain readable identity views and suppress unavailable mutations.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: modules/custom-objects/services/persistence/custom-object-records.ts (sharedActiveObject);
  modules/custom-objects/services/persistence/custom-object-endpoints.ts'
---

# Read-only records under inactive definitions

## Context

Retiring a category must stop maintenance without making existing references and history unreadable.

## Decision

Ordinary custom-record changes require an active category, while retained records under inactive definitions remain readable by identity and removable through applicable cascades.

## Alternatives Considered

Hiding every inactive-category record: References and retained historical navigation would lose their readable targets. Continuing direct writes after retirement: Archival would cease to be an effective boundary for ordinary maintenance. Stopping cascades at inactive categories: Owner deletion could violate the continuing ownership policy and leave dependants behind.

## Consequences

Record writes hold a shared parent lock while checking active status. Screens retain readable identity views and suppress unavailable mutations.