The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | commerce_obligation_worker | Receive a permanent application refusal. | CAP-COM-FUL-004 | The register retains its failure code and creates a delivery exception. | test services-commerce:modules/fulfillment/tests/integration/services/register/obligation-worker.integration.spec.js#fails the obligation with the participant’s code, raises obligation_failed, and acknowledges the item |
| 2 | /console/{tenantId}/orders/operations | Open Operations and choose the failed-delivery group. | CAP-COM-FUL-008 | The adapter supplies findings with order, customer and age context. | test react-console:lib/commerce/operations/__tests__/live.test.ts#reads the open and acknowledged findings of each service kind, every page, and completes the shown rows from the order |
| 3 | acknowledgeOperationalException | Acknowledge the exception with an explanation. | CAP-COM-FUL-008 | Its state and order history reflect staff awareness. | test services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js#acknowledges then resolves the finding, with the interventions logged, the order’s history and the audit events recorded |
| 4 | reauthorizeObligation | Re-authorize failed work with a recorded reason. | CAP-COM-FUL-005 | A fresh instruction is sent and the fixture application refuses it again. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#re-authorizes the failed obligation at sequence two, which the participant fails again, then resolves it with its exceptions |
| 5 | resolveObligation | Resolve the failed obligation with its settlement result. | CAP-COM-FUL-005 | The obligation and its open exceptions become resolved. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#re-authorizes the failed obligation at sequence two, which the participant fails again, then resolves it with its exceptions |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 1 | The application never answers its instruction. | Redispatch once at acknowledgement expiry, then record lost acknowledgement. | A finding identifies the missing acknowledgement. | test services-commerce:modules/fulfillment/tests/integration/services/register/register-sweeper.integration.spec.js#fails it ack_lost on the next deadline, with the exception raised and the history line written |
| alternate | 4 | Staff have evidence that in-flight delivery completed. | Use service-side manual completion with evidence. | Completion is retained and a subsequent application callback is rejected. | test services-commerce:modules/fulfillment/tests/e2e/obligation-holds.e2e.spec.js#refuses the participant’s late callback as not in flight, leaving the manual completion |
| failure | 4 | Staff lack recovery authority. | The menu marks re-authorization unavailable with its permission explanation. | No recovery instruction is submitted. | test react-console:lib/commerce/operations/__tests__/rules.test.ts#asks each intervention for its own key, so holding one does not offer another |
| Id | Statement | Provenance |
|---|---|---|
01 | Staff interventions retain their reasons in the intervention log and order history. | test services-commerce:modules/operations/tests/e2e/operations.e2e.spec.js#acknowledges then resolves the finding, with the interventions logged, the order’s history and the audit events recorded |
02 | Obligation resolution closes its related open exceptions. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#re-authorizes the failed obligation at sequence two, which the participant fails again, then resolves it with its exceptions |
03 | Recovery uses a fresh authorization and obsolete authorization cannot change its outcome. | test services-commerce:modules/fulfillment/tests/integration/services/persistence/obligation-register.integration.spec.js#issues the next authorization for a failed obligation, naming the previous and superseding it; refuses any other state |
End-to-end policy: required: Operations is a live console workflow that changes order work; adapter unit tests and service tests provide partial evidence, but an end-to-end browser scenario is still needed.