---
id: ADR-CRM-ENT-001
title: Entities Owns the Classification Types
product_area: crm
module: entities
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-crm: 7ea48a414c42eade10d60753b8bcc323b1dd726f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Entities owns every classification catalogue used by its contacts,
  organizations and affiliations; a separate configuration function serves
  catalogue routes to keep deployment size manageable; it does not establish
  another product owner.
constrains:
  - SVC-CRM-ENT-configuration-types
  - SVC-CRM-ENT-entities
  - DOM-CRM-ENT-001
  - DOM-CRM-ENT-002
  - DOM-CRM-ENT-003
  - RESP-CRM
origin: 'OQ-CRM-ENT-002 decided 2026-10-22 by Andrew: B'
alternatives:
  - option: Move catalogue ownership into a separate product module.
    why_not: >-
      The recorded product decision retains ownership with the records
      classified, giving each policy one specification home.
  - option: Place all catalogue routes in the main Entities function.
    why_not: >-
      The function split addresses the deployment resource budget without
      changing ownership.
consequences:
  - Catalogue rules and screens belong to Entities capabilities.
  - The route-hosting service owns no independent Domain Object.
  - The remaining product-area registration conflict stays open.
evidence:
  - >-
    rhythm-v2-docs: specs/crm/entities/FINDINGS.md (OQ-CRM-ENT-002,
    FND-CRM-ENT-016)
  - >-
    services-crm at 7ea48a41:
    modules/configuration-types/aws/api/configuration-types.routes.ts (header)
---
# Entities Owns the Classification Types

## Context

The product decision already settled catalogue ownership. This record cites that answer and explains its deployment consequence rather than asking for the same boundary decision again.

## Decision

Entities owns every classification catalogue used by its contacts, organizations and affiliations; a separate configuration function serves catalogue routes to keep deployment size manageable; it does not establish another product owner.

## Alternatives Considered

Move catalogue ownership into a separate product module. The recorded product decision retains ownership with the records classified, giving each policy one specification home.

Place all catalogue routes in the main Entities function. The function split addresses the deployment resource budget without changing ownership.

## Consequences

The two service contracts describe different route hosts within one product module. Object ownership remains with Entities. A remaining registry row still implies another module and must be reconciled separately within its authorized scope.

Catalogue rules and screens belong to Entities capabilities. The route-hosting service owns no independent Domain Object. The remaining product-area registration conflict stays open.