01must proveProposed | Payment reversal or refund, dispute or chargeback opening and invoice reopening affect only the identified lines' delivered or in-progress obligations, leaving waiting obligations untouched. origin: D-P5-01 (build decision, not a product ruling): services-commerce:docs/migrations/operations/README.md#D-P5-01 no proof recorded yet | policy | service | test |
02must proveProposed | The default review response records enforcement and raises a staff-review exception without instructing the delivering application. origin: Decision E, Andrew 2026-10-18 (review by a person, as built): services-commerce:docs/migrations/operations/README.md#Section 5 walkthrough no proof recorded yet | policy | service | test |
03must proveProposed | Notify and suspend responses immediately authorize and queue an unconditional enforcement obligation while retaining the original completed obligation. no proof recorded yet | lifecycle | service | test |
04must proveProposed | A cancel-line response sends the enforcement instruction and also raises a review for staff to complete cancellation and its financial consequences. origin: Decision F, Andrew 2026-10-18 (staff finish the money side, as built): services-commerce:docs/migrations/operations/README.md#Section 5 walkthrough; D-P5-02 no proof recorded yet | policy | service | test |
05Proposed | The none reversal response leaves the delivered line unchanged. | policy | service | test |
06must proveProposed | A reversal without an explaining cancellation raises one informational refund-without-cancellation exception for each delivered order. no proof recorded yet | policy | service | test |
07must proveProposed | The same obligation and financial event produce at most one enforcement, including when the event is redelivered. no proof recorded yet | invariant | service, database | test |
08must proveProposed | Restored funds produce one restoration for each enforcement that acted, dispatching it where the application supports restoration and otherwise leaving it for staff. no proof recorded yet | lifecycle | service | test |
09must proveProposed | Enforcement accepts only its defined transitions through pending, dispatched, completed, restored, failed and resolved states. no proof recorded yet | lifecycle | service | test |
10must proveProposed | Staff resolution requires a reason and resolution, closes the enforcement-review exception, and rejects readers and repeated resolution. no proof recorded yet | permission | api, service | test |
11Proposed | Enforcement read authority permits lists by order or state and inspection of an individual enforcement. | permission | api | observed |