---
id: ADR-CRM-REG-012
title: No Regional Operation Is Published to Submissions
product_area: crm
module: regions
revision: 2
status: proposed
design_intent: proposed
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  The regional surface publishes no Submissions-compatible operation and records a reason for each current
  exclusion.
constrains:
  - SVC-CRM-REG-regions
origin: 'R2-ARCH-002 v2.0 (Andrew, 2026-10-22) rule 1, publish or say why not; the precedent ADR-CRM-ENT-015'
alternatives:
  - option: Expose regional definition creation to intake.
    why_not: >-
      The current operation maintains authorized workspace configuration; an intake use would require its own
      capture authority and binding.
consequences:
  - Future regional intake requires a separately specified submission contract and version.
supersedes: []
evidence:
  - 'services-crm at a8d1364f: modules/regions/aws/api/regions.routes.ts; no Submissions binding declared.'
---

# No Regional Operation Is Published to Submissions

## Context

The cited submission architecture requires a published version or an explicit exclusion for every operation. The regional route declarations expose no submission binding.

## Decision

The contract records each exclusion: configuration maintenance, existing-data reads, saved-policy preview, recalculation or bulk-job management. These reasons describe the scoped surface without approving a future intake capability.

## Alternatives Considered

Expose regional definition creation to intake. The current operation maintains authorized workspace configuration; an intake use would require its own capture authority and binding.

## Consequences

Future regional intake requires a separately specified submission contract and version.