---
id: TST-CRM-REG-066
title: Deployed regional assignment lifecycle
kind: api-lifecycle
product_area: crm
module: regions
revision: 1
status: draft
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
repository: services-crm
files:
  - tests/e2e/dev/regions.dev.spec.ts
implements:
  - ATS-CRM-REG-002-01
  - ATS-CRM-REG-008-02
  - ATS-CRM-REG-008-03
  - ATS-CRM-REG-010-01
  - ATS-CRM-REG-011-05
  - FAS-CRM-REG-04-01
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 15
isolation: >-
  Run-named records in the configured development workspace; policy-changing runs snapshot and restore
  shared settings and require exclusive scheduling.
evidence:
  - 'services-crm:tests/e2e/dev/regions.dev.spec.ts'
assertions:
  - scenario: ATS-CRM-REG-002-01
    source: 'services-crm:tests/e2e/dev/regions.dev.spec.ts#refuses to delete a region in use'
  - scenario: ATS-CRM-REG-008-02
    source: >-
      services-crm:tests/e2e/dev/regions.dev.spec.ts#moves the contact when its address moves to another
      region
  - scenario: ATS-CRM-REG-008-03
    source: 'services-crm:tests/e2e/dev/regions.dev.spec.ts#clears the region when the address matches no rule'
  - scenario: ATS-CRM-REG-010-01
    source: 'services-crm:tests/e2e/dev/regions.dev.spec.ts#changes no contact when the rules are saved'
  - scenario: ATS-CRM-REG-011-05
    source: 'services-crm:tests/e2e/dev/regions.dev.spec.ts#moves the contact to its region under the new rules'
  - scenario: FAS-CRM-REG-04-01
    source: 'services-crm:tests/e2e/dev/regions.dev.spec.ts#moves the contact to its region under the new rules'
binding_scope: >-
  Exact assertion anchors identify the contribution of this file. Scenario-level bindings may compose
  several files; registration does not assert that every file alone executes every scenario step.
---

# Deployed regional assignment lifecycle

## Verification Boundary

The suite calls development services and uses their public record reads to inspect regional outcomes. Browser journeys may also cover work outside Regions; this register counts only the regional assertions.

## What This Suite Proves

The linked source assertions contribute checks for references block removal; moving the deciding address changes placement; lost deciding input clears calculated placement; policy saves preserve existing placements; recalculation applies changed coverage; explicit recalculation applies saved coverage. A scenario spanning several files relies on those assertions together; this file supplies only its named checks.

## What It Does Not Prove

The register establishes neither a current passing run nor verified conformance. Unbound scenarios, broader feature chains and the delegated infrastructure beyond this execution boundary remain unproved.

## Real Dependencies and Test Doubles

Development APIs and the configured authentication environment are real dependencies. Browser journeys can intercept a specifically named fault; persona availability and cleanup are part of the suite source.

## Must Not Be Doubled

Regional matching, regional persistence and the stored values under assertion must remain real. A substitute answer for these dependencies cannot qualify the linked regional outcomes.