--- id: FAS-MBR-STR-02 title: 'Organizational Units: Feature Acceptance Suite' feature: FEAT-MBR-STR-02 product_area: membership module: structure revision: 1 status: proposed product_intent: proposed source_sha: services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 scenarios: - id: FAS-MBR-STR-02-01 title: 'Prepare a chapter’s identity, organization and dues context' kind: behaviour exercises: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 relies_on: - ATS-MBR-STR-006-05 - ATS-MBR-STR-007-03 - ATS-MBR-STR-008-01 preconditions: >- Configured custom fields, organization references and a prepared chapter-dues product are available. steps: - do: >- Create a chapter with local details and custom values, add its legal organization and extend the dues product, then read all three facets. expect: Each facet refers to the same continuing unit identity and returns its own saved details. provenance: proposed source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 expected: Each facet refers to the same continuing unit identity and returns its own saved details. negative: false data_needs: >- Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions. bound_to: [] provenance: proposed source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - id: FAS-MBR-STR-02-02 title: Local detail edits preserve legal and financial context kind: interaction exercises: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 relies_on: - ATS-MBR-STR-006-02 - ATS-MBR-STR-007-06 - ATS-MBR-STR-008-05 preconditions: A chapter already has a legal link and versioned financial settings. steps: - do: >- Replace contact details, end the legal link and replace finance settings using each applicable version. expect: >- The accepted edits keep unit placement intact and preserve separate link history and financial versions. provenance: proposed source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 expected: >- The accepted edits keep unit placement intact and preserve separate link history and financial versions. negative: false data_needs: >- Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions. bound_to: [] provenance: proposed source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - id: FAS-MBR-STR-02-03 title: A merged chapter retains follow-up work kind: lifecycle exercises: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - CAP-MBR-STR-003 relies_on: - ATS-MBR-STR-003-03 - ATS-MBR-STR-003-07 - ATS-MBR-STR-003-09 - ATS-MBR-STR-007-08 - ATS-MBR-STR-008-05 preconditions: 'The source carries legal, settlement and dues records.' steps: - do: >- Merge the source, inspect its follow-up result, attempt a detail replacement and separately update its organization and finance facets. expect: >- Ordinary source details are protected after merging while retained organization and finance work remains separately addressable. provenance: test source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - CAP-MBR-STR-003 - >- services-membership:tests/acceptance/structure/MBR-ACC-0018.acceptance.ts#the link and the settings replace both answer 200 expected: >- Ordinary source details are protected after merging while retained organization and finance work remains separately addressable. negative: false data_needs: >- Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions. bound_to: - TST-MBR-STR-077 - >- services-membership:tests/acceptance/structure/MBR-ACC-0018.acceptance.ts#the link and the settings replace both answer 200 provenance: test source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - CAP-MBR-STR-003 - >- services-membership:tests/acceptance/structure/MBR-ACC-0018.acceptance.ts#the link and the settings replace both answer 200 - id: FAS-MBR-STR-02-04 title: Unit administration requires workspace management kind: permission exercises: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 relies_on: - ATS-MBR-STR-019-01 - ATS-MBR-STR-019-03 preconditions: 'A reader, workspace administrator and unit-scoped officer have access contexts.' steps: - do: 'Compare detail, link and dues inspection with detail, link and finance changes for each caller.' expect: >- Read and manage authority are enforced consistently; local officer authority alone does not authorize workspace setup. provenance: proposed source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 expected: >- Read and manage authority are enforced consistently; local officer authority alone does not authorize workspace setup. negative: true data_needs: >- Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions. bound_to: [] provenance: proposed source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - id: FAS-MBR-STR-02-05 title: A stale detail replacement leaves associated work intact kind: regression exercises: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 relies_on: - ATS-MBR-STR-006-06 - ATS-MBR-STR-007-06 - ATS-MBR-STR-008-04 preconditions: Two editors read a chapter that already has legal and dues context. steps: - do: >- Save the first detail edit, send the second at the old version and inspect the unit, links and dues. expect: The second write fails and preserves the accepted details and all associated records. provenance: proposed source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 expected: The second write fails and preserves the accepted details and all associated records. negative: true data_needs: >- Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions. bound_to: [] provenance: proposed source: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 evidence: - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - CAP-MBR-STR-003 - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 - CAP-MBR-STR-006 - CAP-MBR-STR-007 - CAP-MBR-STR-008 regression_record: - revision: 1 change: initial scenarios: - FAS-MBR-STR-02-01 - FAS-MBR-STR-02-02 - FAS-MBR-STR-02-03 - FAS-MBR-STR-02-04 - FAS-MBR-STR-02-05 reason: Initial cumulative feature coverage from the landed planning and design contracts. provenance: documented source: specs/CONVENTIONS.md#5.3 Feature Acceptance Suite (FAS) narrative_sources: - section: What the Feature Must Do as a Whole provenance: proposed source: FEAT-MBR-STR-02 - section: Interactions Between Capabilities provenance: proposed source: - FAS-MBR-STR-02-02 - section: Regression Record provenance: documented source: specs/CONVENTIONS.md#5.3 Feature Acceptance Suite (FAS) --- # Organizational Units: Feature Acceptance Suite ## What the Feature Must Do as a Whole The suite follows one unit across its descriptive, legal and financial context. Each scenario combines outcomes that staff need to trust together and identifies the capability examples it relies on. ## Interactions Between Capabilities Replace contact details, end the legal link and replace finance settings using each applicable version. The accepted edits keep unit placement intact and preserve separate link history and financial versions. A complete feature run also revisits the accepted and refused outcomes when referenced configuration changes. Proposed cases require executable proof before they establish delivery qualification. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish cumulative feature coverage from the landed planning and design contracts. |