Commercial Licensing: Feature Acceptance Suite

What the Feature Must Do as a Whole

Commercial licensing must remain explainable as contracts and deliberate staff exceptions change. The feature cases connect replacement, exception history and staff review, including provider outages and refused writes.

Interactions Between Capabilities

Review a withhold and its withdrawal. Staff see the active refusal become restored standing while the withdrawn decision retains author and time.

Preserve a commercial copy through outage and cancellation. Failure preserves the copy; cancellation replaces its coverage while separate staff history remains.

Proposed chains require an executable suite that performs the complete sequence. Separate lower-level bindings do not establish whole-feature execution.

Regression Record

Revision	Change	Scenario	Why
1	initial	all	Establish cumulative whole-feature proof from the landed planning and design contracts.

Show evidence (sources, provenance, origins, pinned commits)

Scenarios

5 scenarios proving FEAT-PFM-OPS-03 as a whole.

01 Explain commercial coverage with retained exceptions behaviour proposed

Exercises: CAP-PFM-OPS-011 CAP-PFM-OPS-012 CAP-PFM-OPS-013
Relies on: ATS-PFM-OPS-011-05 ATS-PFM-OPS-012-08 ATS-PFM-OPS-013-01
Preconditions: A workspace has company coverage and an existing staff exception.
Steps: [object Object]
Expected: Staff can relate the current coverage to commercial evidence and independent exception history.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Source: ATS-PFM-OPS-011-05; ATS-PFM-OPS-012-08; ATS-PFM-OPS-013-01

02 Review a withhold and its withdrawal interaction test

Exercises: CAP-PFM-OPS-011 CAP-PFM-OPS-013
Relies on: ATS-PFM-OPS-011-04 ATS-PFM-OPS-013-02 ATS-PFM-OPS-013-03
Preconditions: A ready licensed application supports staff exception management.
Steps: [object Object]
Expected: Staff see the active refusal become restored standing while the withdrawn decision retains author and time.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Bound to: TST-PFM-OPS-050
Source: react-console:e2e/dev/hq-licensing.dev.spec.ts#the licensing panel withholds an application on the development tenant with a reason, and revokes it

03 Preserve a commercial copy through outage and cancellation lifecycle proposed

Exercises: CAP-PFM-OPS-011 CAP-PFM-OPS-012 CAP-PFM-OPS-013
Relies on: ATS-PFM-OPS-012-08 ATS-PFM-OPS-012-10 ATS-PFM-OPS-012-13
Preconditions: A synchronized company licenses a workspace that also has staff decisions.
Steps: [object Object]
Expected: Failure preserves the copy; cancellation replaces its coverage while separate staff history remains.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Source: ATS-PFM-OPS-012-08; ATS-PFM-OPS-012-10; ATS-PFM-OPS-012-13

04 Separate commercial readership from decision making permissionnegative proposed

Exercises: CAP-PFM-OPS-011 CAP-PFM-OPS-012 CAP-PFM-OPS-013
Relies on: ATS-PFM-OPS-011-08 ATS-PFM-OPS-012-12 ATS-PFM-OPS-013-01
Preconditions: Staff readers, staff managers and customer administrators have different authority.
Steps: [object Object]
Expected: Readers can inspect permitted evidence; only managers change it and customer context cannot use HQ actions.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Source: ATS-PFM-OPS-011-08; ATS-PFM-OPS-012-12; ATS-PFM-OPS-013-01

05 Preserve deliberately withdrawn grants during reseeding regression proposed

Exercises: CAP-PFM-OPS-011 CAP-PFM-OPS-012 CAP-PFM-OPS-013
Relies on: ATS-PFM-OPS-011-09 ATS-PFM-OPS-012-09 ATS-PFM-OPS-013-02
Preconditions: A development workspace has a withdrawn seed grant and a retained company copy.
Steps: [object Object]
Expected: Neither repeated seeding nor absent configuration recreates the withdrawn decision or removes its history.
Data: An isolated workspace, owned test records and caller contexts named in the preconditions.
Source: ATS-PFM-OPS-011-09; ATS-PFM-OPS-012-09; ATS-PFM-OPS-013-02

Planning

Commercial Licensing: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

Interactions Between Capabilities ​

Regression Record ​

Scenarios

Commercial Licensing: Feature Acceptance Suite

What the Feature Must Do as a Whole

Interactions Between Capabilities

Regression Record