15 acceptance test sets for MOD-CRM-REG, one per capability, holding 101 scenarios — 89 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-CRM-REG-001 | Maintain the region catalogue | 9 | 7 | 5 | 8 api · 1 unit | Proposed |
ATS-CRM-REG-002 | Retire regions while preserving their references | 6 | 4 | 3 | 4 api · 2 browser | Proposed |
ATS-CRM-REG-013 | Restrict regional work to authorised users | 6 | 5 | 5 | 1 unit · 3 browser · 2 api | Proposed |
ATS-CRM-REG-014 | Import a catalogue of regions | 3 | 2 | 2 | 1 browser · 1 unit · 1 api | Proposed |
ATS-CRM-REG-015 | Share regions through record references and exports | 1 | 0 | 0 | 1 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-REG-003 | Configure automatic placement and its address sources | 7 | 7 | 4 | 7 api | Proposed |
ATS-CRM-REG-004 | Build the geographic assignment policy | 8 | 7 | 6 | 8 api | Proposed |
ATS-CRM-REG-005 | Maintain individual rules alongside the shared policy | 7 | 6 | 4 | 7 api | Proposed |
ATS-CRM-REG-006 | Determine an address’s geographic region | 9 | 9 | 3 | 7 unit · 2 api | Proposed |
ATS-CRM-REG-007 | Check an address against the saved policy | 5 | 5 | 2 | 5 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-REG-008 | Keep placements aligned with address changes | 14 | 12 | 0 | 14 api | Proposed |
ATS-CRM-REG-009 | Preserve a deliberate regional exception | 4 | 4 | 1 | 4 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-REG-010 | Identify placements that need recalculation | 7 | 6 | 0 | 7 api | Proposed |
ATS-CRM-REG-011 | Apply the current policy across existing records | 9 | 9 | 1 | 1 unit · 8 api | Proposed |
ATS-CRM-REG-012 | Monitor recalculation and recover from failure | 6 | 6 | 2 | 6 api | Proposed |