---
id: ADR-CRM-ENT-014
title: Activate Cross-service Behaviors Through Deployment Switches
product_area: crm
module: entities
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-crm: 7ea48a414c42eade10d60753b8bcc323b1dd726f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Date reconciliation, owner-deletion policy and attention publishing are
  deployment-controlled; pinned defaults enable the first two in development,
  disable them in production and leave attention off without explicit
  configuration; deployed runtime values were not inspected.
constrains:
  - WF-CRM-ENT-006
  - WF-CRM-ENT-009
  - WF-CRM-ENT-004
  - SVC-CRM-ENT-entities
  - RESP-CRM
origin: >-
  the Work Coordinator deploy-order rule (Andrew, 2026-10-18); D-46 (Andrew,
  2026-10-19); CRM-Q10 amendment (Andrew, 2026-10-19); OQ-CRM-ENT-007 open
alternatives:
  - option: Enable all dependencies unconditionally.
    why_not: >-
      A deployment could invoke a missing cross-service capability and fail
      ordinary business work.
  - option: Expose these controls as workspace settings.
    why_not: >-
      That runtime product configuration is not implemented and would move a
      deployment-order concern into another contract.
consequences:
  - >-
    Pinned defaults imply different development and production behavior for date
    settlement and association deletion.
  - >-
    Planning and comments describing both switches as disabled everywhere
    conflict with the current defaults.
  - >-
    Activation requires a recorded rollout decision; static defaults do not
    prove a running environment’s state.
evidence:
  - >-
    services-crm at 7ea48a41:
    aws/cdk/resources/affiliation-date-reconciliation.ts; aws/crm.names.ts
    (CRM_OWNER_DELETION_RULES_BY_ENVIRONMENT, attentionPublishingEnabled);
    lib/attention.ts
---
# Activate Cross-service Behaviors Through Deployment Switches

## Context

These switches manage dependency readiness and background effects. The pinned code establishes deployment defaults, but this examination did not inspect live configuration or deploy anything.

## Decision

Date reconciliation, owner-deletion policy and attention publishing are deployment-controlled; pinned defaults enable the first two in development, disable them in production and leave attention off without explicit configuration; deployed runtime values were not inspected.

## Alternatives Considered

Enable all dependencies unconditionally. A deployment could invoke a missing cross-service capability and fail ordinary business work.

Expose these controls as workspace settings. That runtime product configuration is not implemented and would move a deployment-order concern into another contract.

## Consequences

The differences from approved planning remain findings. A rollout decision must identify the intended production behavior and its prerequisites before preparation treats development behavior as representative.

Pinned defaults imply different development and production behavior for date settlement and association deletion. Planning and comments describing both switches as disabled everywhere conflict with the current defaults. Activation requires a recorded rollout decision; static defaults do not prove a running environment’s state.