---
id: TST-MBR-MEM-060
title: Merge treatment of current and future connections
kind: api-lifecycle
product_area: membership
module: memberships
revision: 1
status: draft
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
repository: services-membership
files:
  - tests/acceptance/affiliations/MBR-ACC-0277.acceptance.ts
implements:
  - ATS-MBR-MEM-008-04
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  A suite-owned workspace and test identifiers; suites that use shared seed data
  require the source’s serial execution and cleanup policy.
verification_notes: >-
  Bindings describe the assertions reviewed at the pinned commit; the suite is
  not executed by this documentation job.
coverage_gap: null
evidence:
  - 'services-membership:tests/acceptance/affiliations/MBR-ACC-0277.acceptance.ts'
assertion_anchors:
  - scenario: ATS-MBR-MEM-008-04
    source: >-
      services-membership:tests/acceptance/affiliations/MBR-ACC-0277.acceptance.ts#MBR-ACC-0277:
      Savannah Chapter is merged into Atlanta: Pat's row is transferred, Kim's
      not-yet-begun row is re-pointed, Jo's duplicate is ended without carrying
      her primary flag, closed rows and a section's rows are left, and Savannah
      can be deactivated but never deleted
---

# Merge treatment of current and future connections

## Verification Boundary

The suite runs an acceptance journey through the in-process API composition with signed contexts, enforcement and PostgreSQL.

## What This Suite Proves

The structured bindings identify the capability and feature cases whose reviewed assertions this suite executes. Source anchors preserve the evidence for each binding.

## What It Does Not Prove

An in-process pass does not qualify deployed network calls, queues, schedules or the member’s full browser journey. Registration records existing code and leaves execution and conformance unverified.

## Real Dependencies and Test Doubles

The API dispatcher, enforcement and PostgreSQL remain real. Test signing keys, controlled business dates, fixture owner rows and any recording partner ports replace deployed dependencies.

## Must Not Be Doubled

Keep the prepared database, workspace boundary, exercised owner constraints and the business operation under test real. A partner double cannot substitute for the Membership write this suite claims to exercise.