It is 09:40 on a Tuesday, and three people are waiting on the same small box. One is rerunning a failing agent test, one is regenerating embeddings for a demo, and one started an overnight batch at 08:55 that still holds every slot. Nobody did anything wrong, and yet the whole afternoon is gone before the interactive work gets a turn.
That opening is an illustrative composite of a pattern, not a log from one team. It has three distinct failure modes, and only the first one is obvious. Name all three before you write policy, because a playbook that fixes blocking but ignores attribution will be quietly abandoned in two weeks.
The three failure modes of a shared free box
1. Head-of-line blocking. A long batch run occupies the only concurrency you have, so short interactive requests queue behind work that nobody is watching. On paid infrastructure you buy your way out; on a free box you have to schedule your way out.
2. Attribution gaps.β¦