---
id: TST-CRM-REG-051
title: Assignment-policy reads and criteria reconstruction
kind: integration
product_area: crm
module: regions
revision: 1
status: draft
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
repository: services-crm
files:
  - >-
    modules/regions/tests/integration/services/persistence/region-assignment-settings.queries.integration.spec.js
implements:
  - ATS-CRM-REG-003-01
  - ATS-CRM-REG-010-02
  - ATS-CRM-REG-010-06
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/integration/services/persistence/region-assignment-settings.queries.integration.spec.js
assertions:
  - scenario: ATS-CRM-REG-003-01
    source: >-
      services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.queries.integration.spec.js#a
      tenant that has saved no settings › answers assignment off, the legacy defaults and no rules, with
      no system properties at all
  - scenario: ATS-CRM-REG-010-02
    source: >-
      services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.queries.integration.spec.js#the
      settings of a tenant that saved them › says a recalculation is needed, because the rules changed
      and none has run since
  - scenario: ATS-CRM-REG-010-06
    source: >-
      services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.queries.integration.spec.js#a
      tenant that has saved no settings › says no recalculation is needed, because a tenant with no
      settings assigns nothing to recalculate
  - scenario: ATS-CRM-REG-010-06
    source: >-
      services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.queries.integration.spec.js#settings
      saved a second time › says no recalculation is needed, because the tenant assigns nothing
      automatically any more
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.
---

# Assignment-policy reads and criteria reconstruction

## Verification Boundary

The suite exercises real regional persistence and processing against the prepared database. It verifies the source assertions linked in this register.

## What This Suite Proves

The linked source assertions contribute checks for unsaved configuration returns defaults; a successful current-generation run clears need; disabled or absent settings suppress need. 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

PostgreSQL and the regional persistence under assertion are real. The suite supplies test execution contexts and fixtures; a local API harness replaces deployed transport where applicable.

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