---
id: ADR-CRM-ENT-010
title: Archive Is Separate from Status
product_area: crm
module: entities
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-crm: 7ea48a414c42eade10d60753b8bcc323b1dd726f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Dedicated administrator archive actions preserve record status, details,
  relationships and history while removing ordinary visibility; aPI and bulk
  deletion remain hard deletion under the recorded decision until safer deletion
  is introduced.
constrains:
  - STATE-CRM-ENT-001
  - STATE-CRM-ENT-002
  - WF-CRM-ENT-009
  - DOM-CRM-ENT-033
  - SCR-CRM-ENT-003
  - SCR-CRM-ENT-007
origin: 'D-02 and D-07 (CRM-M1); CRM-Q10 and its amendment (Andrew, 2026-10-19)'
alternatives:
  - option: Represent archive as another status.
    why_not: >-
      That would replace the person or organization status and prevent
      preserving it independently.
  - option: Replace current deletion with soft deletion alone.
    why_not: >-
      The required broader safety checks are not available under the current
      milestone contract.
consequences:
  - >-
    Record pages provide archive; hard deletion remains an authorized API or
    bulk operation.
  - 'Organization relationships block deletion, while archive can retain them.'
  - >-
    Enabled Platform owner-deletion policy supplies the association guard;
    deployment defaults disable it outside development.
evidence:
  - >-
    services-crm at 7ea48a41: docs/archive.md;
    docs/milestones/CRM-M1-contacts-and-organizations.md (D-02, D-07, CRM-Q10)
---
# Archive Is Separate from Status

## Context

Archive offers a reversible way to set aside a record while retaining its standing and relationships. Unarchive clears archive metadata without forcing an active status.

## Decision

Dedicated administrator archive actions preserve record status, details, relationships and history while removing ordinary visibility; aPI and bulk deletion remain hard deletion under the recorded decision until safer deletion is introduced.

## Alternatives Considered

Represent archive as another status. That would replace the person or organization status and prevent preserving it independently.

Replace current deletion with soft deletion alone. The required broader safety checks are not available under the current milestone contract.

## Consequences

The recorded product decision retains hard deletion for authorized API and bulk callers. Archive does not replace its protection and dependency checks. Cross-application association policy is conditional on deployment activation.

Record pages provide archive; hard deletion remains an authorized API or bulk operation. Organization relationships block deletion, while archive can retain them. Enabled Platform owner-deletion policy supplies the association guard; deployment defaults disable it outside development.