---
id: ADR-PFM-TNL-016
title: Dedicated Deletion Commands
product_area: platform
module: tenant-lifecycle
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: Use dedicated deletion commands instead of record replacement, with reason and reviewed-version checks
  on preservation actions.
constrains:
- DOM-PFM-TNL-005
- SVC-PFM-TNL-tenants
- WF-PFM-TNL-010
- SCR-PFM-TNL-003
origin: services-platform:docs/standards/record-write-contracts.md#W1 Version preconditions (D-05, D-35, D-52);
  services-platform:docs/tenants/tenant-lifecycle-plan.md#§8.2
alternatives:
- option: Edit the request as a record with a complete replacement payload
  why_not: Replacement could alter workflow-owned dates, standing or decision attribution.
consequences:
- Hold, release and cancellation refuse a stale reviewed version.
- Current schedule-resume and purge-retry routes remain exceptions without reason or version inputs.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: modules/tenants/aws/api/tenant-deletion-requests.{routes,schemas}.ts; services/deletion/deletion-holds.ts;
  docs/standards/record-write-contracts.md.'
---

# Dedicated Deletion Commands

## Context

Deletion standing and eligibility belong to controlled decisions. A replacement payload would expose fields that staff actions must not freely overwrite.

## Decision

Use dedicated deletion commands instead of record replacement, with reason and reviewed-version checks on preservation actions.

## Alternatives Considered

Edit the request as a record with a complete replacement payload: Replacement could alter workflow-owned dates, standing or decision attribution.

## Consequences

Hold, release and cancellation refuse a stale reviewed version. Current schedule-resume and purge-retry routes remain exceptions without reason or version inputs.