Rhythm 2.0 Specifications

Appearance

CAP-COM-FUL-009Detect stalled and inconsistent order work

Markdown

CAP-COM-FUL-009

Detect stalled and inconsistent order work

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationPartially observed

Planning

Feature
FEAT-COM-FUL-02
Key concepts
CON-COM-FUL-003
Actors
ACT-COM-013
Journeys
JNY-COM-FUL-002
Related
CAP-COM-FUL-007, CAP-COM-FUL-008
Proved by
ATS-COM-FUL-009

KindCapabilityProduct areaCommerceModuleFulfillment, Shipping and InventoryRevision1

Read atservices-commerce c8b66a98

Detect stalled and inconsistent order work ​

Purpose ​

Scheduled checks surface order work that stops progressing or disagrees with its records.

How It Works ​

The reconciler selects checks according to the current clock. Each check reads candidates using its own budget and records what it finds. Problems become staff findings where that check implements a finding path. Actions needed for recovery are delegated to the process that owns the work. A failing check is recorded while other due checks continue. Some declared checks remain placeholders, and queue-depth monitoring creates a metric rather than a staff exception. The product should define ownership and response for each monitored failure before relying on the schedule operationally.

Relationships ​

  • Complete the financial work requested by a post-sale document supplies or consumes related delivery records.
  • Review and resolve operations findings supplies or consumes related delivery records.

The Formal Contract

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

Outcomes
Scheduled detection can identify problems before a customer reports them.Checks delegate financial and delivery changes to the owning process.
Surfaces
job

Controls

35 controls apply, from the corpus control catalogue.

TC-IAM-006 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-CRY-001 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-LOG-004 TC-LOG-005 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-007 TC-AVL-004 TC-MON-001 TC-MON-002 TC-MON-004 TC-PI-001 TC-PI-002 TC-PI-004 TC-PI-005 TC-VEN-001 TC-VEN-002 TC-VEN-003 TC-PRV-001 TC-PRV-002

Business Rules

10 rules, 7 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.

IdRuleKindEnforced atProvenance
01must prove
Proposed
The minute reconciler runs checks due every minute, every fifth minute, hourly at minute zero or daily at 02:00 UTC, and records a thrown check while continuing the others.
origin: D-P5-07 (build decision, not a product ruling): services-commerce:docs/migrations/operations/README.md#D-P5-07
no proof recorded yet
lifecycleservicetest
services-commerce:modules/operations/tests/integration/services/reconciler/reconciler.integration.spec.js#reads each cadence off the clock
02must prove
Proposed
Unbilled placed orders older than ten minutes are counted, blocked candidates raise billing-blocked findings, and other candidates raise placed-without-invoice findings once sixty minutes old.
no proof recorded yet
calculationserviceobserved
services-commerce:modules/operations/services/reconciler/reconciler.ts:RECONCILER_CHECKS
03must prove
Proposed
Payment uncertainty lasting fifteen minutes, accepted lines missing invoice links after ten minutes, reservation holds ten minutes beyond expiry and migrated obligations blocked thirty days raise findings in their workspace; window-voided orders receive one informational finding.
no proof recorded yet
calculationservicetest
services-commerce:modules/operations/tests/integration/services/reconciler/reconciler.integration.spec.js#raises tender_uncertain, the window’s tender_window_expired once, accepted_without_invoice_line, hold_stranded and migrated_unfulfilled, each in its tenant
04must prove
Proposed
Adjustments active for fifteen minutes are resumed, except processor-only refunds, which wait until their request is a day old.
origin: COMM-M1 R7-2 (repair report, not a product ruling): services-commerce:docs/milestones/COMM-M1-repairs-7-report.md#R7-2
no proof recorded yet
lifecycleservicetest
services-commerce:modules/operations/tests/integration/services/reconciler/reconciler.integration.spec.js#raises refund_without_cancellation once for the reversal the handler never saw, and resumes the stale adjustment to completion
05must prove
Proposed
The reversal backstop raises one informational refund-without-cancellation exception for each order reached through recent reversal receipts, without inspecting cancellation documents.
no proof recorded yet
policyserviceobserved
services-commerce:modules/operations/services/reconciler/reconciler.ts:RECONCILER_CHECKS
06
Proposed
The hourly dead-letter check publishes queue depth as a metric without creating an operational exception.
policyserviceobserved
services-commerce:modules/operations/services/reconciler/reconciler.ts:RECONCILER_CHECKS
07must prove
Proposed
Daily checks raise one discount-drift finding per affected order from the previous two days and retain one recurring counter-drift finding per promotion or code whose use count disagrees with redemptions.
origin: Decision I, Andrew 2026-10-18 (promotion drift checks): services-commerce:docs/migrations/promotions/README.md#B8; docs/migrations/operations/README.md#D-P5-17
no proof recorded yet
calculationservicetest
services-commerce:modules/operations/tests/integration/services/reconciler/reconciler.integration.spec.js#raises promotion_discount_drift for the order of the window whose discount its allocations do not add up to, with the figures
08
Proposed
Reconciliation delegates actions to the owning keyed process instead of directly modifying money or application-delivered records.
invariantserviceobserved
services-commerce:modules/operations/services/reconciler/reconciler.ts:runReconciler
09must prove
Proposed
Cross-workspace candidate reads require their sweep permissions and reject an existing transaction; resulting findings are written in each record's workspace.
no proof recorded yet
invariantservice, databasetest
services-commerce:modules/operations/tests/integration/services/persistence/reconciler-candidates.queries.integration.spec.js#refuses every read inside another transaction
10
Proposed
Scheduled-amendment, overdue-return and inventory-balance checks remain skipped, while stale-obligation and acknowledgement handling remain delegated to the checkout sweep.
policyservicetest
services-commerce:modules/operations/tests/integration/services/reconciler/reconciler.integration.spec.js#measures the dead-letter queue through the port, records the sweeper’s two passes as its, and the waiting checks with their reason

Scenarios

IdGivenWhenThenProvenance
01An unblocked order has waited an hour for billing.Run reconciliation alongside an eleven-minute-old unblocked fixture.The older order receives a missing-invoice exception and the younger order is only counted.test
services-commerce:modules/operations/tests/integration/services/reconciler/reconciler.integration.spec.js#raises placed_without_invoice for the hour-old unbilled order and billing_blocked for the blocked one, and counts the eleven-minute one without raising

Edge Cases

IdGivenWhenThenProvenance
02Staff resolved an order's discount-drift exception.Run the next daily drift check on the same order.The existing resolved finding prevents another exception for that order.test
services-commerce:modules/operations/tests/integration/services/reconciler/reconciler.integration.spec.js#finds the order again and raises it nothing more: the resolved finding stands (D-P5-08)

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software