Loop Definitions
@betterdata/loop-definitions publishes serializable first-party loop definitions that describe allowed states and transitions.
What A Loop Definition Contains
Each published definition includes:- Identity:
scope,name,version,loopId,industry - Metadata:
description, publisher, publication timestamp, license - State machine:
initialState,terminalStates,exceptionStates,transitions
Six First-Party Definitions
| Name | Loop ID | Transition profile |
|---|---|---|
scm-procurement | scm.procurement | PO confirmation, receipt scheduling, goods received, invoice match, close/dispute |
scm-fulfillment | scm.fulfillment | Reserve, pick, pack, ship, close |
scm-quality | scm.quality | Quality placeholder with blocked/close semantics |
scm-replenishment | scm.replenishment | Threshold breach, replenishment trigger, PO confirmation, close |
dcm-order | dcm.order | Confirm, allocation pending, allocated/fail, shipped, close/cancel |
dcm-returns | dcm.returns | RMA approve/reject, receive, damaged hold/restock, credit, close |
Registry Access
- Browse: registry.betterdata.co/loop-definitions
- Example lookup:
External Use Cases
- Validate event choreography against allowed transitions
- Build loop dashboards and monitoring overlays
- Generate compliance-facing transition maps for audits