Attention
Five things should have moved and did not. Nothing that is moving normally appears on this page.
Resolves any identifier to its object. Addresses the single gap that blocked every concept in scenario S3 — and it matters most here, because anything that is not stalled has no other route in.
Stalled now
5 · oldest 9 daysRanked by a rule the console applies and does not let you see: a paid patient who cannot be ordered for comes above paperwork, then oldest first. Anything the rule ranks below the fold is a stall nobody works.
-
1 · No catalog item is pinned
stuck 6 days
Pin a catalog item -
2 · Two catalog items disagree
stuck 5 days
Choose which one -
3 · Four vials short, and nothing recorded since
9 days
lane
Record what arrived -
4 · Sent, arrival never confirmed
6 days
Confirm arrival -
5 · Draft never transmitted
4 days
Transmit it
Everything else is moving — 96 paid fills across 15 preparations are ready to order. That is the whole day's throughput, and this one line is the only route to it.
The same screen on a good day
0 stallsThis is the honest failure mode, not a nicety. On a clean day the home screen says nothing at all, a new operator has nowhere to start, and the only thing left to click is Everything — a surface this concept treats as secondary.
What this page assumes
- The home screen is only what stopped. The 96 paid fills that are the actual day's work are deliberately absent. That is the concept's central bet and its central risk: five rows tell an operator nothing about whether today is busy or empty.
- Every stall derives from an observed state or a record's own created_at / sent_at. No supplier lead time, minimum quantity or delivery estimate is used to decide that something is late.
- The rank order is policy written in code and invisible on the screen. Paid patients above paperwork, then oldest first. Nobody in the console can see the rule or change it, and anything it ranks low is a stall nobody works.
- Two of the five resolution controls cannot be built today. Nothing in either lane re-pins a catalog item, and no acknowledgement state exists, so "Confirm arrival" has nothing to confirm against — the row surfaces a gap it cannot close.
- The row marked lane needs PR #926's data model. On PR #1059's model a partial receipt is not representable at all and this 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.