---
id: TST-CRM-REG-062
title: Retained assignment integration compatibility
kind: integration
product_area: crm
module: regions
revision: 1
status: draft
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
repository: services-crm
files:
  - modules/regions/tests/legacy/rolodex-regions/tests/integration/assign-region.int.spec.js
implements:
  - ATS-CRM-REG-008-01
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 2
isolation: Suite-owned workspace and records in the prepared test database.
evidence:
  - 'services-crm:modules/regions/tests/legacy/rolodex-regions/tests/integration/assign-region.int.spec.js'
  - 'services-crm:modules/regions/tests/legacy/rolodex-regions/src/logic/assign-region.js'
  - 'services-crm:modules/regions/tests/legacy/rolodex-regions/src/lambda/events.js'
  - 'services-crm:package.json#test:unit, test:integration, test:e2e'
assertions:
  - scenario: ATS-CRM-REG-008-01
    source: >-
      services-crm:modules/regions/tests/legacy/rolodex-regions/tests/integration/assign-region.int.spec.js#Assign
      Regions › Contacts › the region has been set
execution_gate: >-
  The package test commands include these retained compatibility files; legacy adapters translate inputs
  into the current regional calculation, persistence or local API harness.
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.
---

# Retained assignment integration compatibility

## Verification Boundary

This retained compatibility suite is included in the current service test commands. Its legacy-shaped inputs pass through adapters to the current regional implementation, so the register counts it as executable regional evidence.

## What This Suite Proves

The linked source assertions contribute checks for placement is a reaction to committed creation. 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

The compatibility harness translates older SDK and storage calls into the current local test infrastructure. Regional persistence and PostgreSQL supply stored outcomes, while legacy clients and transport are adapters rather than deployed services.

## 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.