The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | placeCheckout (Orders module) | Place the member's order with the applicable delivery policies. | CAP-COM-FUL-001 | The register contains each line's pending work and saved gate. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#lists each order’s one pending obligation with the built-in default gate frozen on it, and refuses a portal member the register |
| 2 | commerce_financial_facts (Accounting change events) | Record payment in Accounting and deliver the affected-line facts. | CAP-COM-FUL-002 | Financially eligible work opens while required approval remains a staff decision. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#resolves each line by Accounting’s invoice line through the facts port, opens three gates and blocks the one that needs approval |
| 3 | approveObligation | Approve the waiting line with an explanation. | CAP-COM-FUL-005 | One approval is retained and its paid obligation becomes authorized. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#releases the blocked obligation on one of five simultaneous approvals, which opens its gate at once since the line is paid, with the one intervention recorded; the other four are refused 409 naming it (DEF-COM-0869) |
| 4 | commerce_obligation_dispatcher, commerce_obligation_worker | Dispatch authorized instructions to the owning applications. | CAP-COM-FUL-004 | Immediate work completes and longer-running work retains progress. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#completes the plain one, leaves the long one in progress and fails the failing one, acknowledging all three |
| 5 | completeObligation | Report completion of the longer-running instruction. | CAP-COM-FUL-004 | The register records completion and replay returns its existing result. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#completes the obligation and answers it as it stands; the repeat answers the same |
| 6 | /console/{tenantId}/orders/{orderId} | Inspect the order's Fulfilment card. | CAP-COM-FUL-005 | The card presents obligations with authorization and attempt detail. | observed react-console:lib/commerce/order-flows/live.ts:createLiveOrderFlowsAdapter |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 2 | The financial event is lost. | A later sweep revisits eligible stale pending work within its page budget. | Selected paid obligations can open, without a fixed recovery-time guarantee. | test services-commerce:modules/fulfillment/tests/integration/services/register/register-sweeper.integration.spec.js#evaluates every stale pending obligation of an accepted order across both tenants, opens the paid ones, and nudges once |
| alternate | 2 | Staff billed the console order on terms. | Evaluate the approved-terms fact under a policy that allows it. | Eligible lines can authorize after acceptance without waiting for payment. | test services-commerce:modules/fulfillment/tests/unit/register/order-billed-on-terms.spec.js#is a console order whose profile requires terms |
| failure | 4 | Delivery receives a permanent refusal. | Record failed delivery and its operational finding. | Operations staff have work to investigate and recover. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#completes the plain one, leaves the long one in progress and fails the failing one, acknowledging all three |
| failure | 3 | Staff submit competing approvals. | Retain the successful approval and reject its competitors. | The obligation has one approval result. | test services-commerce:modules/fulfillment/tests/unit/register/obligation-approval.spec.js#names the approval that stands, who and when, in the message and the details |
| Id | Statement | Provenance |
|---|---|---|
01 | Concurrent eligibility evaluation retains one authorization for each paid line's delivery. | test services-commerce:modules/fulfillment/tests/integration/services/persistence/obligation-register.integration.spec.js#answers the second not waiting once the first committed, and the register holds ONE authorization |
02 | Approval-required work waits until its staff approval is recorded. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#resolves each line by Accounting’s invoice line through the facts port, opens three gates and blocks the one that needs approval |
03 | Financial receipt and gate-opening history retain Accounting's correlation reference. | test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#writes the fact and the opening on the orders’ histories, with Accounting’s event and correlation id |
End-to-end policy: required: This journey crosses financial facts, delivery coordination and the console; service evidence covers its backend stages, but no existing browser test proves the full interaction.