Skip to main content

​
Loops - The Atomic Unit

A loop is a state machine that tracks one business process from open to terminal state, with transition-level evidence.

​
What Is A Loop?

1

Loop opens

An initiating event starts the loop instance (for example, PO created or order confirmed).
2

Transitions execute

Domain events move the instance through allowed states with guard and side-effect handling.
3

Loop closes

A terminal state is reached (such as CLOSED, CREDITED, or CANCELLED based on loop design).
4

History is queryable

Full transition history remains available for operations, debugging, and compliance export.

​
Loop Anatomy

{
  "loopId": "scm.procurement",
  "aggregateId": "PO-2026-0012",
  "state": "RECEIPT_SCHEDULED",
  "openedAt": "2026-02-15T09:00:00Z",
  "transitions": [
    {
      "from": "OPEN",
      "to": "PO_CONFIRMED",
      "triggeredBy": "scm.procurement.po_confirmed.v1",
      "actorId": "user:drew.kim",
      "occurredAt": "2026-02-17T14:23:00Z",
      "correlationId": "corr_abc123"
    }
  ]
}

​
Six First-Party Loop Types

Loop IDDescriptionTypical aggregateTerminal states
scm.procurementPO lifecycle orchestrationPurchase OrderCLOSED, DISPUTED
scm.fulfillmentOutbound fulfillment executionShipmentCLOSED
scm.qualityQuality assessment and dispositionLot / Return lotCLOSED
scm.replenishmentReorder orchestration from demand signalSKU-locationCLOSED
dcm.orderCustomer order lifecycleOrderCLOSED, CANCELLED
dcm.returnsRMA and return lifecycleRMACLOSED

​
Monitoring Loops

  • Record-level loop status is visible in SCM workflows tied to that aggregate.
  • Admin-facing loop monitor surfaces cross-loop diagnostics for platform operators.
  • API consumers can query transition streams for custom observability and analytics.

​
Loop Completion And Billing

Loop completions are measured when an instance reaches a terminal state.
See platform pricing for committed volume details.