Concept A · queue-first
Fulfillment
Everything waiting on a person, in the order it should be handled.
Resolves any identifier to its object. Addresses the single gap that blocked every concept in scenario S3.
Work waiting
6 bucketsRecently done
All ordersWhat this page assumes
- The home screen is the work list. There are no summary tiles. Every row is a thing to do, and clicking it starts the doing.
- Exceptions sit at the top of the same list rather than on their own screen. An operator who does not know a stall exists never chooses a filter that would reveal it — so stalls are ordered above routine work instead of hidden behind one.
- Every bucket derives from an observed state or from a record's own created_at / sent_at. No supplier lead time or minimum quantity is used anywhere.
- The two buckets marked lane require PR #926's data model. On PR #1059's model they do not exist and the list is four rows.
- Search is shown here because scenario S3 failed identically under all three concepts. It is a required capability, not a concept feature.
- The zero-count bucket is deliberately still rendered but greyed — a queue that vanishes when empty teaches operators it does not exist.