FLOW-0002 — Replenishment Absorbs Shop-Floor Chaos

The happy path repeats, lap after lap; the shop floor does not cooperate. Cards get withdrawn mid-lap, replenishment runs produce nothing, requests get pulled back out of order queues, and every lap eventually rolls into the next one. This scenario shows how each departure reconciles itself — the replenishment machinery detaches signals, cancels emptied demand, and releases materials, with no one keeping a cleanup list.

Use cases traversed

This flow is a path across use cases, in order. Identifiers are the immutable prefix form defined in the naming convention; a flow is not a level-4 scenario.

Domains crossed: Resources, Operations, Procurement.

Step	Use case	What happens
1	RES::KC::0004	A card moves between cycle states
2	RES::KC::0005	A queued card is withdrawn or re-queued
3	PRO::OQ::0003	The queue is viewed and filtered
4	OPS::DEM::0001	Demand collation absorbs the change
5	RES::KC::0007	Kanban state is read by procurement

The business value: exceptions cost an operator one action, not a supervisor an afternoon — replenishment is self-healing rather than exception-driven.

Actors and domains

• Sam Scansworth — shop floor. Drives the ordinary rollover.
• Irene Itemsworth — inventory manager. Withdraws cards and reports failed replenishments.
• David Dealsworth — procurement. Shelves a request pulled back out of a never-submitted order.

The diagram conventions — the domain colors, the dependency ordering, and the arrow meanings — are those of the scenario catalog.

The scenario at domain level

One announcement, two endings

A lap ends exactly two ways, and they are distinct on the record: it rolls over into the next lap (recorded as completed) or it is withdrawn (recorded as abandoned — final; a card withdrawn and later re-requested reads as abandoned, not completed). Either way the same announcement fires, and Demand reacts the same way: the ended trip’s signal is detached from whatever demand item held it. (The withdrawal announcement ships today; extending it to rollover closures is designed but not yet built — see the Kanban Cards page.)

What the demand item does with a detached signal — continue with its remaining signals, or cancel itself if left empty with nothing else expected — is the reconciliation branch drawn in the pull-replenishment round trip.

The corrective exceptions have names

The redesigned lap machine is forward-only — a card advances along its lap, skipping only stages its site doesn’t perform — plus exactly two named corrective exceptions, each an explicit operation rather than an arbitrary jump:

• Shelve — a request that entered an order queue is pulled back out, allowed only while the order was never submitted. The card returns to requesting; nothing downstream ever knew about it.
• Report production failure — a replenishment attempt produced nothing for this card. The card returns to the request queue, and any materials attached to the run are released.

The refusal in the last exchange is the discipline that makes the first two trustworthy: because arbitrary jumps are refused, a card’s history is a record of what happened, not of what someone clicked.

Where the behavior is specified

• Kanban Cards — the lap machine, rollover, withdraw, the two corrective exceptions, and the completed/abandoned distinction.
• Demand — the trip-ended listener and the self-canceling demand item.
• The pull-replenishment round trip — the happy path all of this protects, and the reconciliation activity diagram.