FAS-CRM-REG-02 Geographic Assignment Policy acceptance
Markdown Planning / CRM / Regions / Feature Acceptance Suite Geographic Assignment Policy acceptance What the Feature Must Do as a Whole The suite connects assignment choices, geographic coverage, individual edits and saved-address preview. Changes are checked through the other capabilities that consume their results.
Interactions Between Capabilities Individual ordering changes saved-policy preview. Preview follows the newly saved geographic order.
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-02 as a whole.
03 Coverage survives a pause in assignment lifecycle proposed
Exercises CAP-CRM-REG-003 CAP-CRM-REG-004 Relies on ATS-CRM-REG-003-02 ATS-CRM-REG-004-07 Preconditions Automatic placement is enabled with saved coverage. Steps Disable assignment without sending a replacement rule list, read the retained policy, then enable again. Expected Coverage remains saved through the pause and reenabling returns the feature to eligible assignment. Data Automatic placement is enabled with saved coverage. Source STATE-CRM-REG-002 04 Policy reading permits preview but cannot save changes permission negative proposed
Exercises CAP-CRM-REG-003 CAP-CRM-REG-004 CAP-CRM-REG-007 Relies on ATS-CRM-REG-007-03 ATS-CRM-REG-013-06 Preconditions A reader has regional read authority without update authority. Steps Read settings and coverage, preview an address, then attempt to open the editor and save settings. Expected Reading and preview remain available; policy editing is refused. Data A reader has regional read authority without update authority. Source SVC-CRM-REG-regions ← Previous Feature Acceptance Suite FAS-CRM-REG-01 · Regional Catalogue acceptance Next Feature Acceptance Suite → FAS-CRM-REG-03 · Record Placements acceptance