Module Status

The functional pages describe the current design — the target the running system is converging on. This table says where each module that the Orders v2 design covers stands between that design and the runtime today. Modules outside that scope — Facilities, Order Queue, Shipping, Shop Access and OAM among them — are not assessed here; their own pages remain the authority, and a status column would claim an assessment nobody made. Each row mirrors the Status line at the top of the module’s own page; the page is the authority, and this table is the at-a-glance aggregation.

Module	Domain	Status	What ships today
Item	reference-data	Live	Built and running; the versioned lifecycle and pin behavior are the design target it is converging on.
Business Affiliate	reference-data	Live	Built and running; same convergence note as Item.
Staff	reference-data	Designed	The one consumer today — the order’s assignee — is still a plain text field.
Kanban Cards	resources	Live (lifecycle redesign in progress)	The module ships; the forward-only lap machine is tightening the live system’s looser behavior.
Inventory Items	resources	Designed — build pending	A live inventory capability exists and is being rebuilt to these rules.
Processing Network	resources	Designed — minimal stub in the runtime	Defined just far enough to anchor the kanban and demand modules.
Demand	operations	In development	Implementation under review (operations PR #219).
Orders	procurement	Designed — build pending	The live system’s order capability is the client-side purchase-order sheet.
Receiving	receiving	Designed — build pending	The live system’s receiving is the lightweight flows in the canonical use cases.

Two readings follow from the table:

• Item, Business Affiliate and the kanban signal are live; Staff is designed, so the reference-data layer is live in two of its three modules. The design’s remaining depth — receiving capture, the order lifecycle, inventory custody, demand collation — is designed and verified, with demand collation first through the build pipeline.
• When a scenario and today’s runtime disagree, the scenario describes the design target. The Business Flows walk the design; this table qualifies which parts you can exercise today.