--- id: FAS-MBR-STR-06 title: 'Setup Governance: Feature Acceptance Suite' feature: FEAT-MBR-STR-06 product_area: membership module: structure revision: 1 status: proposed product_intent: proposed source_sha: services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 scenarios: - id: FAS-MBR-STR-06-01 title: Provision setup and maintain versioned records kind: behaviour exercises: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 relies_on: - ATS-MBR-STR-020-01 - ATS-MBR-STR-018-03 - ATS-MBR-STR-019-02 preconditions: A new isolated workspace is licensed and has an authorized setup administrator. steps: - do: >- Provision relationship purposes, create configuration, read its version and submit an accepted edit followed by a stale edit. expect: >- Provisioning supplies its standard context and configuration changes respect authority and the accepted version. provenance: proposed source: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 expected: >- Provisioning supplies its standard context and configuration changes respect authority and the accepted version. 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-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 - id: FAS-MBR-STR-06-02 title: Loaded setup remains subject to ordinary read and save safeguards kind: interaction exercises: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 relies_on: - ATS-MBR-STR-020-04 - ATS-MBR-STR-020-05 - ATS-MBR-STR-018-08 preconditions: >- Parent-first structure and dependent configuration load inputs are prepared beside a separate workspace. steps: - do: >- Load and reconcile valid setup, then read and update those records from their own and the foreign workspace contexts. expect: >- Loaded records follow the same authority and isolation boundary as ordinary records; the foreign context sees no owned record. provenance: proposed source: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 expected: >- Loaded records follow the same authority and isolation boundary as ordinary records; the foreign context sees no owned record. 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-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 - id: FAS-MBR-STR-06-03 title: Reset preserves catalogues and purge preserves neighbours kind: lifecycle exercises: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 relies_on: - ATS-MBR-STR-020-02 - ATS-MBR-STR-020-03 - ATS-MBR-STR-020-01 preconditions: 'Two dedicated workspaces contain setup, with lifecycle states prepared for reset and deletion.' steps: - do: >- Reset the first structure, inspect retained catalogues, then purge it in deleting state and inspect the neighbour. expect: >- Reset retains kind catalogues; purge removes the selected workspace’s structural data and versions while the neighbour remains whole. provenance: proposed source: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 expected: >- Reset retains kind catalogues; purge removes the selected workspace’s structural data and versions while the neighbour remains whole. 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-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 - id: FAS-MBR-STR-06-04 title: Setup families reject insufficient workspace authority kind: permission exercises: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 relies_on: - ATS-MBR-STR-019-02 - ATS-MBR-STR-019-03 - ATS-MBR-STR-019-04 preconditions: 'Administrator, read-only staff, officer and unlicensed callers are prepared.' steps: - do: >- Compare program and configuration reads and saves, then attempt the licensed application operation with insufficient admission. expect: >- Only the declared workspace management grants authorize saves, and licensing and application checks precede work. provenance: proposed source: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 expected: >- Only the declared workspace management grants authorize saves, and licensing and application checks precede work. 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-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 - id: FAS-MBR-STR-06-05 title: A failed setup save leaves earlier valid work intact kind: regression exercises: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 relies_on: - ATS-MBR-STR-018-06 - ATS-MBR-STR-020-05 preconditions: An authorized migration has saved valid preceding configuration records. steps: - do: >- Submit an invalid package child list, inspect earlier records and the absent failed aggregate, correct the item and retry. expect: >- Earlier valid records survive, the failed aggregate contains no partial lists and the corrected retry can proceed. provenance: proposed source: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 expected: >- Earlier valid records survive, the failed aggregate contains no partial lists and the corrected retry can proceed. 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-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 evidence: - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 - CAP-MBR-STR-018 - CAP-MBR-STR-019 - CAP-MBR-STR-020 regression_record: - revision: 1 change: initial scenarios: - FAS-MBR-STR-06-01 - FAS-MBR-STR-06-02 - FAS-MBR-STR-06-03 - FAS-MBR-STR-06-04 - FAS-MBR-STR-06-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-06 - section: Interactions Between Capabilities provenance: proposed source: - FAS-MBR-STR-06-02 - section: Regression Record provenance: documented source: specs/CONVENTIONS.md#5.3 Feature Acceptance Suite (FAS) --- # Setup Governance: Feature Acceptance Suite ## What the Feature Must Do as a Whole The suite follows workspace setup across provisioning, authorized changes and removal. Each scenario combines outcomes that staff need to trust together and identifies the capability examples it relies on. ## Interactions Between Capabilities Load and reconcile valid setup, then read and update those records from their own and the foreign workspace contexts. Loaded records follow the same authority and isolation boundary as ordinary records; the foreign context sees no owned record. 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. |