Understand and intervene in an order's delivery

Purpose

Operations staff explain outstanding delivery and record exceptional manual decisions.

How It Works

Staff inspect the register for an order and open an obligation's detail. They review its gate, delivery attempts and intervention history before deciding what to do. The service offers distinct approval, hold, override, recovery, resolution and manual-completion actions. Each action has its own authority and records the explanation supplied by the person acting. The console currently exposes only part of that service workflow. Audit publication also remains limited by the selected provider. The product should give staff consistent access to the supported interventions and their consequences.

Relationships

Carry authorized work to its delivering application supplies or consumes related delivery records.
Choose delivery conditions for sold items supplies or consumes related delivery records.
Review and resolve operations findings supplies or consumes related delivery records.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Staff can explain the outstanding delivery on an order.Manual decisions retain attribution for later review.
Surfaces: consoleapi

Controls

24 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-CRY-001 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`commerce.obligations.read`	api	tenant
`commerce.obligations.approve`	api	tenant
`commerce.obligations.override`	api	tenant
`commerce.obligations.reauthorize`	api	tenant
`commerce.obligations.resolve`	api	tenant
`commerce.obligations.hold`	api	tenant
`commerce.obligations.complete-manually`	api	tenant
`orders.obligations.view`	console	tenant

Business Rules

10 rules, 9 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Staff can list an order's obligations by line and unit and inspect gates, states, authorizations, attempts and interventions; portal callers cannot read the register. proved by `ATS-COM-FUL-001-11`, `ATS-COM-FUL-002-12`, `ATS-COM-FUL-005-01`, `ATS-COM-FUL-005-08`, `TST-COM-FUL-022`	permission	api	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
`02`must prove Proposed	Staff interventions require a reason, first append the acting person and reason to the intervention log, and add an order-history entry. proved by `ATS-COM-FUL-005-02`, `TST-COM-FUL-021`, `TST-COM-FUL-022`, `TST-COM-FUL-025`, `TST-COM-FUL-039`	validation	api, service, database	test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#refuses an approval to a reader, 403 permission_missing, and without a reason, 400
`03`must prove Proposed	One approval can release and immediately evaluate an obligation awaiting approval, while competing approvals are rejected with the successful approval identified. origin: DEF-COM-0869 (acceptance defect) proved by `ATS-COM-FUL-005-03`, `TST-COM-FUL-022`, `TST-COM-FUL-040`, `TST-COM-FUL-054`	lifecycle	service, database	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)
`04`must prove Proposed	A separately authorized sensitive override opens a waiting obligation regardless of its gate facts and retains the overriding person and time. proved by `ATS-COM-FUL-005-04`, `TST-COM-FUL-022`, `TST-COM-FUL-040`	permission	api, service	test services-commerce:modules/fulfillment/tests/e2e/obligation-register.e2e.spec.js#overrides the gate of the unpaid obligation, authorizing it regardless of the facts, with the override on the obligation
`05`must prove Proposed	Only failed obligations accept re-authorization with a new sequence or staff resolution, and resolution also closes their open exceptions. proved by `ATS-COM-FUL-003-07`, `ATS-COM-FUL-005-04`, `ATS-COM-FUL-005-09`, `ATS-COM-FUL-005-11`, `ATS-COM-FUL-008-07`, `ATS-COM-FUL-008-09`, `TST-COM-FUL-022`, `TST-COM-FUL-040`	lifecycle	service, database	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
`06`must prove Proposed	A hold keeps a waiting obligation blocked despite payment, release immediately evaluates it, and holds cannot be placed on authorized obligations or released from unheld ones. proved by `ATS-COM-FUL-005-05`, `TST-COM-FUL-021`, `TST-COM-FUL-039`	lifecycle	service	test services-commerce:modules/fulfillment/tests/e2e/obligation-holds.e2e.spec.js#keeps the gate shut while the hold stands, though the line is paid and Accounting’s event arrives
`07`must prove Proposed	Manual completion requires both reason and evidence, applies only to delivery in flight, closes the authorization and rejects a later application callback. proved by `ATS-COM-FUL-004-10`, `ATS-COM-FUL-005-06`, `ATS-COM-FUL-005-10`, `TST-COM-FUL-021`, `TST-COM-FUL-039`	validation	api, service	test services-commerce:modules/fulfillment/tests/e2e/obligation-holds.e2e.spec.js#refuses the manual completion without the evidence (400) and to a reader (403), then completes it with the records and the note
`08`must prove Proposed	Each intervention requires its specific administrator permission; register read authority permits no intervention. proved by `ATS-COM-FUL-005-02`, `TST-COM-FUL-021`, `TST-COM-FUL-022`, `TST-COM-FUL-025`, `TST-COM-FUL-039`	permission	api	observed services-commerce:modules/fulfillment/aws/api/fulfillment.routes.ts
`09` Proposed	An intervention calls the selected audit provider without rolling back if publication fails; the Platform provider currently writes an error log instead of storing a Platform audit event.	policy	service	observed services-commerce:modules/fulfillment/services/register/intervention-audit.ts
`10`must prove Proposed	The Fulfilment card exposes re-authorization, resolution, hold release and gate override under their individual permissions, with no controls for approval, placing holds or manual completion. proved by `ATS-COM-FUL-005-07`	permission	console	observed react-console:lib/commerce/order-flows/live.ts:obligationRoutes

Scenarios

Id	Given	When	Then	Provenance
`01`	A paid obligation is waiting for approval.	Submit five staff approvals concurrently.	One attributed approval opens the gate and the competing requests conflict with it.	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)
`02`	An application has not answered an in-progress instruction.	Record manual completion with delivery evidence.	The obligation completes and a subsequent callback cannot change that result.	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

Planning

Implementation

Understand and intervene in an order's delivery ​

Purpose ​

How It Works ​

Relationships ​