FAS-CRM-REG-01 Regional Catalogue acceptance
Markdown Planning / CRM / Regions / Feature Acceptance Suite Regional Catalogue acceptance What the Feature Must Do as a Whole The suite connects catalogue maintenance, retirement, authority, import and export around the same regional identity. It checks both successful staff work and retained dependencies.
Interactions Between Capabilities Imported definitions enter the same maintained catalogue. One stable definition connects import, maintenance and export.
Regression Record Revision Change Scenario Why 1 initial all Establish cumulative feature coverage from the landed specifications and pinned executable assertions.
Show evidence (sources, provenance, origins, pinned commits)Scenarios 5 scenarios proving FEAT-CRM-REG-01 as a whole.
02 Imported definitions enter the same maintained catalogue interaction proposed
Exercises CAP-CRM-REG-001 CAP-CRM-REG-014 CAP-CRM-REG-015 Relies on ATS-CRM-REG-014-03 ATS-CRM-REG-015-01 Preconditions A valid file defines a region with an integration identifier. Steps Import it, inspect and rename the region, then export the catalogue. Expected One stable definition connects import, maintenance and export. Data A valid file defines a region with an integration identifier. Source WF-CRM-REG-005 04 Regional readers cannot maintain the catalogue permission negative test
Exercises CAP-CRM-REG-001 CAP-CRM-REG-013 Relies on ATS-CRM-REG-013-04 Preconditions A signed-in identity has regional reading alone. Steps Inspect the region list and its editing actions. Expected The catalogue is readable and no usable create, edit or delete action is available. Data A signed-in identity has regional reading alone. Bound to Source react-console:e2e/dev/regions.dev.spec.ts #shows a read-only user the regions, and offers them nothing that changes one Next Feature Acceptance Suite → FAS-CRM-REG-02 · Geographic Assignment Policy acceptance