SpecificationsOperational Records
16 acceptance test sets for MOD-PFM-OPS, one per capability, holding 191 scenarios — 120 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-OPS-001 | Complete background work with a durable record | 17 | 8 | 7 | 10 unit · 7 api | Proposed |
ATS-PFM-OPS-002 | Resolve interrupted background work | 12 | 9 | 5 | 9 api · 3 unit | Proposed |
ATS-PFM-OPS-003 | Notify a job’s requester of its outcome | 13 | 8 | 3 | 3 unit · 10 api | Proposed |
ATS-PFM-OPS-004 | Recover or deliberately stop background work | 11 | 6 | 3 | 6 unit · 1 browser · 4 api | Proposed |
ATS-PFM-OPS-005 | Inspect background runs within customer reach | 10 | 9 | 5 | 8 api · 2 browser | Proposed |
ATS-PFM-OPS-006 | Investigate platform jobs in Rhythm HQ | 6 | 3 | 1 | 4 api · 2 browser | Proposed |
ATS-PFM-OPS-007 | Inspect jobs across Rhythm services | 8 | 6 | 3 | 6 api · 2 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-OPS-008 | Remember a person’s visits to records | 13 | 10 | 8 | 9 api · 1 unit · 3 browser | Proposed |
ATS-PFM-OPS-009 | Review a person’s record-view history | 7 | 6 | 4 | 1 unit · 6 api | Proposed |
ATS-PFM-OPS-010 | Preserve a shared record-activity trail | 13 | 8 | 8 | 13 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-OPS-011 | Make a reasoned exception to application licensing | 17 | 11 | 6 | 15 api · 2 unit | Proposed |
ATS-PFM-OPS-012 | Derive application licences from commercial contracts | 19 | 13 | 7 | 6 unit · 13 api | Proposed |
ATS-PFM-OPS-013 | Explain workspace licensing to Rhythm staff | 9 | 4 | 1 | 6 api · 3 browser | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-OPS-014 | Resolve a workspace’s application availability | 15 | 10 | 1 | 10 unit · 5 api | Proposed |
ATS-PFM-OPS-015 | Prepare and operate workspace applications | 15 | 6 | 3 | 15 api | Proposed |
ATS-PFM-OPS-016 | Explain application availability to a customer administrator | 6 | 3 | 1 | 6 api | Proposed |