---
id: JNY-MBR-STR-002
title: Reorganize a branch and retain its earlier reporting context
feature: FEAT-MBR-STR-01
product_area: membership
module: structure
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
supersedes:
  - MBR-ACC-0012
  - MBR-ACC-0013
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
actor: ACT-MBR-001
goal: Relocate Atlanta while keeping prior regional reporting and membership affiliations interpretable.
capabilities:
  - CAP-MBR-STR-002
  - CAP-MBR-STR-005
screens: []
steps:
  - 'n': 1
    surface: listOrganizationalUnitDescendants
    action: Inspect Atlanta’s placement in the Eastern Region before restructuring.
    capability: CAP-MBR-STR-005
    expected: The earlier structural context includes Atlanta in Eastern.
    provenance: inferred
    source: >-
      services-membership:tests/e2e/s09-restructuring.e2e.spec.ts#scenario 9: organizational restructuring ›
      files Atlanta under the Eastern Region in September’s snapshot, taken before the move
    note: >-
      Regional placement is established by the snapshot assertion, while the journey’s descendants request is
      inferred from the shared structure.
  - 'n': 2
    surface: moveOrganizationalUnit
    action: Relocate Atlanta beneath Pacific and record the explanation.
    capability: CAP-MBR-STR-002
    expected: The unit’s current branch changes and the placement periods describe the transition.
    provenance: test
    source: >-
      services-membership:tests/e2e/s09-restructuring.e2e.spec.ts#scenario 9: organizational restructuring ›
      moves Atlanta under the Pacific Zone
  - 'n': 3
    surface: listOrganizationalUnitDescendants
    action: Inspect the new current regional context.
    capability: CAP-MBR-STR-005
    expected: Atlanta appears in Western’s current structure and related membership views follow that placement.
    provenance: inferred
    source: >-
      services-membership:tests/e2e/s09-restructuring.e2e.spec.ts#scenario 9: organizational restructuring ›
      shows Jo under the Western Region and the Pacific Zone today, and no longer under the Eastern Region
    note: Roster assertions demonstrate membership visibility that depends on the current structural branch.
  - 'n': 4
    surface: listOrganizationalUnitDescendants
    action: Request Eastern’s structure for the earlier period-end date.
    capability: CAP-MBR-STR-005
    expected: That dated branch still includes Atlanta.
    provenance: test
    source: >-
      services-membership:tests/e2e/s09-restructuring.e2e.spec.ts#scenario 9: organizational restructuring ›
      still holds Atlanta among the Eastern Region’s descendants as of the period end
  - 'n': 5
    surface: listOrganizationalUnitParentHistory
    action: Inspect Atlanta’s retained parent periods.
    capability: CAP-MBR-STR-002
    expected: The periods distinguish Southeast before the change from Pacific afterward.
    provenance: test
    source: >-
      services-membership:tests/acceptance/structure/MBR-ACC-0012.acceptance.ts#MBR-ACC-0012 scenario 9:
      Atlanta moves to the Pacific Zone
alternates:
  - from_step: 2
    condition: Staff use an earlier effective date within the current period.
    path: The corrected period begins on that earlier date.
    outcome: A reader using earlier knowledge can still reproduce the preceding arrangement.
    provenance: test
    source: >-
      services-membership:modules/structure/tests/integration/services/persistence/organizational-units.integration.spec.ts#organizational
      units in the database › the parent history and the as-of tree › answers nothing for a known_at before
      the moves were recorded, beyond the tree as it was then known
failures:
  - from_step: 2
    condition: Staff choose tomorrow as the effective day.
    path: The date check rejects the relocation.
    outcome: The previous arrangement remains intact.
    provenance: test
    source: >-
      services-membership:modules/structure/tests/integration/services/persistence/organizational-units.integration.spec.ts#organizational
      units in the database › the parent history and the as-of tree › refuses a move dated after today
rules_in_play:
  - BR-CAP-MBR-STR-002-01
  - BR-CAP-MBR-STR-002-02
  - BR-CAP-MBR-STR-002-06
  - BR-CAP-MBR-STR-002-07
  - BR-CAP-MBR-STR-002-09
  - BR-CAP-MBR-STR-002-14
  - BR-CAP-MBR-STR-005-01
  - BR-CAP-MBR-STR-005-02
assertions:
  - id: AS-JNY-MBR-STR-002-01
    statement: 'Jo’s affiliation retains its identity, version and unit after the relocation.'
    provenance: test
    source: >-
      services-membership:tests/e2e/s09-restructuring.e2e.spec.ts#scenario 9: organizational restructuring ›
      rewrites no affiliation: Jo’s row is the same row, version and unit
  - id: AS-JNY-MBR-STR-002-02
    statement: The earlier period-end view still includes Atlanta beneath Eastern.
    provenance: test
    source: >-
      services-membership:tests/e2e/s09-restructuring.e2e.spec.ts#scenario 9: organizational restructuring ›
      still files Atlanta under the Eastern Region in a September restated after the move: the period end’s
      tree
e2e_policy: optional
e2e_reason: >-
  The API restructuring case supplies existing evidence. The product should add browser proof when staff can
  perform this workflow through a structure screen.
proved_by: []
---

# Reorganize a branch and retain its earlier reporting context

## Story

Atlanta’s regional responsibility changes, so the administrator relocates its branch beneath Pacific. Current views then place the chapter within Western. The administrator compares that result with the earlier period-end view and checks the retained parent periods. The comparison explains the restructuring without treating Jo’s unchanged chapter affiliation as a member transfer.