Every architecture diagram you have ever drawn contains a pun.
There, between two services, sits the queue. The English “queue” is from the French word for a tail, a line of things waiting. Then a perfect homophone of “cue,” theatre’s word for the precise moment something must happen. The pun is two words describing opposite philosophies of work.
Jobs Wait. Cues Belong to a Moment.
It’s the jobs, tasks, and tickets that actually sit in the industry’s queues. Listen to those words for a second. A job is anonymous piecework, a ticket is a stub, numbered, torn off, thrown away once it’s processed. Each word treats work as fungible cargo, measured by throughput, belonging to no particular moment. A job that runs at 2:14 instead of 2:04 is just a job that ran a little later.
Now go backstage and watch a stage manager call a show. In the prompt book, which crews just call “the book,” the master copy with every technical action written into the margins of the script, nothing in there is a job. Everything is a cue, and a cue carries things.
A cue belongs to a moment, lives at a specific point in the performance, not “eventually,” but right there, after that line, on that breath. It gets called twice before it fires: first “Standby, LX 12,” the operator answers “standing by,” and only then “LX 12… GO.” Skip the standby and nothing happens. Every cue also has an owner. One person calls the show, and every cue has a caller and an operator, so when something fires, everyone in the building knows exactly who said go. And a cue has weight. If you call the cue early, you ruin the scene; call it late and you ruin the scene, too. Nobody has ever said either of those sentences about a ticket.
What Changes When a Queue Becomes a Cue.
We run our AI pipelines on this vocabulary. Our queue is a queue of cues. Nothing enters without admission, nothing fires without its conditions met, and everything belongs to a performance and lands its receipt when it’s done.
This isn’t just wordplay. Turning a “job” into a cue makes you answer three things that ticket thinking does not. What performance does this belong to? Since jobs float free but cues always have a show. What has to be true before it fires? Since jobs get priorities but cues get standby conditions. And who called it? Since jobs get picked up by whoever is available but cues get called by someone accountable. Run every item in your queues through those three and a surprising amount of quiet risk surfaces: retries nobody actually owns, a batch firing at the wrong moment for a downstream system nobody bothered to map, an “eventually” that a regulator is going to ask about someday.
The tech industry got it right (perhaps by accident, which is usually how it goes) by naming the structure a queue, when it had “buffer” and “hopper” and “backlog” sitting right there, and the word for a tail of waiting.
Your queue was full of cues all along. Start calling the show.