SpecificationsWorkspace Lifecycle Across Applications
18 acceptance test sets for MOD-PFM-TNL, one per capability, holding 135 scenarios — 134 of them already bound to an existing test. A scenario names the rules and journey assertions it proves; it never restates them.
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-TNL-001 | Request a complete customer workspace | 7 | 7 | 4 | 7 api | Proposed |
ATS-PFM-TNL-002 | Open a workspace after its applications are ready | 7 | 7 | 2 | 1 unit · 6 api | Proposed |
ATS-PFM-TNL-003 | Understand and recover a workspace build | 9 | 9 | 2 | 9 api | Proposed |
ATS-PFM-TNL-004 | Prepare the customer’s first access and sender | 9 | 9 | 3 | 7 api · 2 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-TNL-005 | Apply workspace availability consistently | 9 | 9 | 4 | 7 api · 2 unit | Proposed |
ATS-PFM-TNL-006 | Preserve valid workspace lifecycle states | 6 | 6 | 4 | 4 api · 2 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-TNL-007 | Account for each application’s lifecycle responsibilities | 7 | 7 | 3 | 4 unit · 3 api | Proposed |
ATS-PFM-TNL-008 | Apply defaults without undoing customer choices | 7 | 7 | 0 | 7 api | Proposed |
ATS-PFM-TNL-009 | Maintain the baseline of existing workspaces | 6 | 6 | 2 | 4 api · 2 unit | Proposed |
ATS-PFM-TNL-010 | Supply application data for workspace exports | 4 | 4 | 1 | 3 api · 1 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-TNL-011 | Control the initial import and subsequent opening | 6 | 6 | 3 | 6 api | Proposed |
ATS-PFM-TNL-012 | Recover an incorrect initial import | 10 | 10 | 5 | 10 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-TNL-013 | Schedule deliberate workspace deletion | 10 | 10 | 5 | 7 api · 3 unit | Proposed |
ATS-PFM-TNL-014 | Pause or cancel deletion while preservation remains possible | 6 | 6 | 3 | 6 api | Proposed |
ATS-PFM-TNL-015 | Keep deletion decisions visible to staff | 5 | 5 | 1 | 1 unit · 4 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-TNL-016 | Revalidate the irreversible deletion decision | 8 | 7 | 2 | 8 api | Proposed |
ATS-PFM-TNL-017 | Remove declared workspace resources and verify the result | 13 | 13 | 4 | 13 api | Proposed |
ATS-PFM-TNL-018 | Retain deletion evidence and prevent identifier reuse | 6 | 6 | 2 | 6 api | Proposed |