PriorityScheduling

Some items should jump the queue — priority scheduling processes higher-priority items first regardless of arrival order, at the risk of starving low-priority ones.

Why we need this / what value this brings

Ensures urgent/high-value work isn't stuck behind routine work in the same queue.

When to use this

When some items genuinely can't wait behind others — but adds real complexity (starvation risk for low-priority items) that isn't worth it otherwise.

How to use or implement this

Implement with a small, fixed number of priority tiers rather than a continuous scale, and guarantee low-priority items eventually get processed (aging) so they don't starve forever.

Research questions

• Would a paid/premium booking or a time-sensitive cancellation ever need to jump ahead of routine queue processing?

---

Empty folder — drop notes, links, and findings here as you research.