The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | listMemberships | Compare the officer’s visible memberships before combination. | CAP-MBR-STR-005 | Alex can see Jo while Pat is outside the officer’s pre-merge view. | test services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah into Atlanta › shows Alex Jo and not Pat before the merge |
| 2 | mergeOrganizationalUnit | Submit Savannah’s combination with Atlanta as survivor. | CAP-MBR-STR-003 | The section relocates and the response counts transferred and duplicate-ended affiliations plus retained leftovers. | test services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah into Atlanta › merges Savannah, counting one affiliation moved and one ended on the survivor |
| 3 | getOrganizationalUnit | Inspect Savannah’s structural record. | CAP-MBR-STR-003 | The source records merged status and identifies Atlanta. | test services-membership:tests/acceptance/structure/MBR-ACC-0018.acceptance.ts#MBR-ACC-0018 Savannah Chapter is merged into Atlanta |
| 4 | listMemberships | Inspect the survivor’s current roster. | CAP-MBR-STR-003 | Atlanta includes Pat and Jo while Savannah’s current roster is empty. | test services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah into Atlanta › lists Jo and Pat on Atlanta’s roster today, and no one on Savannah’s |
| 5 | deleteOrganizationalUnit | Attempt to remove Savannah after the combination. | CAP-MBR-STR-004 | Retained affiliation history prevents removal. | test services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah into Atlanta › refuses to delete Savannah while affiliations name it (unit_has_affiliations) |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 2 | Jo already has an overlapping Atlanta affiliation. | The source affiliation ends without another survivor affiliation being created. | Jo retains the existing Atlanta relationship. | test services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah into Atlanta › keeps Jo’s Atlanta affiliation and ends her Savannah one yesterday |
| failure | 2 | The planned combination introduces a membership unit-rule conflict. | The operation rejects the entire merge and identifies the affected holding. | The original unit and affiliation records remain intact. | test services-membership:modules/structure/tests/integration/services/tree/unit-merge.integration.spec.ts#the tree edits affiliations bind › a merge an affiliation cannot follow › changes nothing: the units, their history and every affiliation, the movable ones included, are as they were |
| Id | Statement | Provenance |
|---|---|---|
01 | Savannah’s merged record identifies Atlanta as survivor. | test services-membership:modules/structure/tests/integration/services/persistence/organizational-units.integration.spec.ts#organizational units in the database › merge › moves the children under the survivor, marks the unit merged and lists what it left |
02 | Pat’s earlier source period ends and the replacement begins at Atlanta. | test services-membership:tests/e2e/s13-unit-merge.e2e.spec.ts#a unit merge moves its members: Savannah into Atlanta › ends Pat’s Savannah affiliation yesterday and continues it in Atlanta as primary from today |
03 | The source’s own detail replacement is refused after merging. | test services-membership:tests/acceptance/structure/MBR-ACC-0018.acceptance.ts#MBR-ACC-0018 Savannah Chapter is merged into Atlanta |
End-to-end policy: optional: Service merge cases and integration evidence cover the current operations. The product should add a browser journey when a screen presents both the merge and its unresolved leftovers.