The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | listOrganizationalUnitDescendants | Inspect Atlanta’s placement in the Eastern Region before restructuring. | CAP-MBR-STR-005 | The earlier structural context includes Atlanta in Eastern. | inferred 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 |
| 2 | moveOrganizationalUnit | Relocate Atlanta beneath Pacific and record the explanation. | CAP-MBR-STR-002 | The unit’s current branch changes and the placement periods describe the transition. | test services-membership:tests/e2e/s09-restructuring.e2e.spec.ts#scenario 9: organizational restructuring › moves Atlanta under the Pacific Zone |
| 3 | listOrganizationalUnitDescendants | Inspect the new current regional context. | CAP-MBR-STR-005 | Atlanta appears in Western’s current structure and related membership views follow that placement. | inferred 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 |
| 4 | listOrganizationalUnitDescendants | Request Eastern’s structure for the earlier period-end date. | CAP-MBR-STR-005 | That dated branch still includes Atlanta. | test 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 |
| 5 | listOrganizationalUnitParentHistory | Inspect Atlanta’s retained parent periods. | CAP-MBR-STR-002 | The periods distinguish Southeast before the change from Pacific afterward. | test services-membership:tests/acceptance/structure/MBR-ACC-0012.acceptance.ts#MBR-ACC-0012 scenario 9: Atlanta moves to the Pacific Zone |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 2 | Staff use an earlier effective date within the current period. | The corrected period begins on that earlier date. | A reader using earlier knowledge can still reproduce the preceding arrangement. | test 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 |
| failure | 2 | Staff choose tomorrow as the effective day. | The date check rejects the relocation. | The previous arrangement remains intact. | test 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 |
| Id | Statement | Provenance |
|---|---|---|
01 | Jo’s affiliation retains its identity, version and unit after the relocation. | test 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 |
02 | The earlier period-end view still includes Atlanta beneath Eastern. | test 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 |
End-to-end policy: optional: The API restructuring case supplies existing evidence. The product should add browser proof when staff can perform this workflow through a structure screen.