FLOW-0005 — Reality at the Dock

Real docks are messy: boxes show up with no order behind them, cartons contain things the manifest never mentioned, and sometimes goods arrive for an item the shop stopped stocking months ago. This scenario shows how each of those cases enters the system as an honest, explicit record — or is refused at the door — without ever corrupting the inventory or the order history.

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: Receiving, Reference Data.

Step	Use case	What happens
1	PRO::RCV::0002	Goods arrive without paperwork
2	PRO::RCV::0003	The receiving list is consulted
3	REF::ITM::0002	An item is looked up or found retired
4	PRO::RCV::0001	The shipment is received or refused

The business value: dock reality is handled inside the system instead of around it — no side spreadsheets, no ghost stock, no records that quietly lie.

Actors and domains

• Keisha Clerkson — receiving. Makes the acceptance decision the blind line embodies.
• Vera Vendorson — the external supplier whose truck occasionally carries surprises.

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

The scenario at domain level

The blind line is the acceptance decision

A line riding an order was vetted when the order was committed — receiving honors it without re-gating, even if its item has since retired. A blind line has no such commitment behind it: adding the line is the moment the shop decides to accept these goods. So the vetting happens there, at the door: a blind line naming a retired item — or an item the catalog has never heard of — is refused outright, and the goods are rejected.

The asymmetry is the point: gates sit at the point of choice, never at propagation — the blind line is a choice; the order-connected line is the consequence of a choice already vetted (the Reference-Data Module Pattern).

Off-manifest is an explicit assertion

Goods that arrive beyond what any paperwork mentioned are not silently folded into a count. The operator asserts the line was off-manifest — a recorded, attributable statement, distinct from the vendor’s stated quantities — and the capture carries that assertion into the frozen record.

Where the behavior is specified

• Receiving — blind lines, the off-manifest assertion, the retired-item refusal, and the freeze.
• Item — the retirement gates: “a retired item is unreceivable, unorderable, unrequestable — for anything new.”
• Inventory Items — the pool a blind line births at its freeze.