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.

Scenarios

5 scenarios proving FEAT-MBR-STR-06 as a whole.

01 Provision setup and maintain versioned records behaviour proposed

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: [object Object]
Expected: Provisioning supplies its standard context and configuration changes respect authority and the accepted version.
Data: Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Source: CAP-MBR-STR-018,CAP-MBR-STR-019,CAP-MBR-STR-020

02 Loaded setup remains subject to ordinary read and save safeguards interaction proposed

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: [object Object]
Expected: Loaded records follow the same authority and isolation boundary as ordinary records; the foreign context sees no owned record.
Data: Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Source: CAP-MBR-STR-018,CAP-MBR-STR-019,CAP-MBR-STR-020

03 Reset preserves catalogues and purge preserves neighbours lifecycle proposed

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: [object Object]
Expected: Reset retains kind catalogues; purge removes the selected workspace’s structural data and versions while the neighbour remains whole.
Data: Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Source: CAP-MBR-STR-018,CAP-MBR-STR-019,CAP-MBR-STR-020

04 Setup families reject insufficient workspace authority permissionnegative proposed

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: [object Object]
Expected: Only the declared workspace management grants authorize saves, and licensing and application checks precede work.
Data: Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Source: CAP-MBR-STR-018,CAP-MBR-STR-019,CAP-MBR-STR-020

05 A failed setup save leaves earlier valid work intact regressionnegative proposed

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: [object Object]
Expected: Earlier valid records survive, the failed aggregate contains no partial lists and the corrected retry can proceed.
Data: Dedicated workspace fixtures, current record versions and distinct callers for the accepted and refused actions.
Source: CAP-MBR-STR-018,CAP-MBR-STR-019,CAP-MBR-STR-020

Planning

Setup Governance: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

Interactions Between Capabilities ​

Regression Record ​

Scenarios

Setup Governance: Feature Acceptance Suite

What the Feature Must Do as a Whole

Interactions Between Capabilities

Regression Record