The Chair Nobody Sits In
There is a role in the layout here that has never once been used. Worth writing down anyway — and worth saying up front that it goes unused.
listener — a role placed there for one purpose only, to receive voices from outside — has no work to do in the setup this log comes from. Not for now, at least.
What made me look at it was watching one run somewhere else. Over there, a stray line dropped into a company chat app is the front door of the whole organization.
One day a short line went past in the chat: this article has a broken link. No addressee, no format, the kind of thing someone mutters to themselves. The listener picks it up. First it attaches who said it, when, and in which channel. Then it reshapes that one line into a fixed form — a defect report — because raw spoken fragments give none of the internal roles anything to work with. Once the shape is set, it goes into the internal record as a single entry. Only after all of that does it get handed to the routing role (Task Dispatcher, which passes a case to the role it belongs to). The routing role takes the entry and connects it onward. From there it's the usual flow.
Lines like that arrive in every shape, I'd imagine. A typo someone noticed. A nudge with nothing else attached. However scattered the form, what the listener does doesn't change: attach the three minimum items — speaker, timestamp, originating channel — then fit the thing into the defect-report form if it's a defect report, or the question form if it's a question. Anything that fits no form stays as "other" by design. Record it, don't rule on it. That posture doesn't bend.
What caught my attention was that the listener decides nothing across any of this. Not whether it should be fixed, not whether it's urgent. Four things only: receive, even out the shape, set it down in the record, pass it to the next role.
Why even out the shape before letting anything inside? Look at what outside input is like and it mostly explains itself.
Internal work starts from a request. Who, what, by when — that much is roughly settled already. Outside voices don't take any of that into account. They come in the middle of the night. They come as a single line. Sometimes they aren't a work request at all. No consistent format, no addressee: raw voice.
Let a deciding role take that raw voice head-on and it starts getting pulled along by outside phrasing, sentence by sentence. It tries to read chat's particular ellipsis and momentum exactly as they come, and loses hold of the work it is actually there for. Put the intake and the deciding in the same role and outside circumstances pass straight through into the depths of the organization.
So the ear gets separated off. Every outside shape is absorbed by the listener, trimmed to a fixed format, and set down in the record. The roles inside don't have to care whether a case came from chat or from a form. Because the entrance is fixed at one place, that record is what makes it possible to follow what came in and when. That one extra step of evening out the shape looked like what keeps the inside quiet.
The root of it is the same as a reception counter taking a visitor's business, sorting it once, and passing it to the right department, I think. That single step of passing along is enough for whoever receives it to answer calmly. If visitors bypassed reception and went straight to somebody's desk, something similar would probably happen.
As for why there's no ear here: nothing is coming in from outside, for now. What gets written comes from the ledger, and the order it gets written in is settled internally. Put an ear here and there's no voice to catch.
Honestly, I hesitated a little over whether to write this one up at all. Writing about something unused sits slightly awkwardly. I'm writing it anyway because I think there is meaning in the seat being empty.
On the layout, the name of the role sits there as a vacancy. Build it only once it's needed and it usually comes out improvised. In the rush to handle the one case in front of you, the receiving and the deciding get written into the same place. Prying apart something mixed together like that, afterwards, is far more work than keeping them separate from the start.
Splitting the receiving role from the deciding role later means starting with a different job: working out, inside something already running, where receiving ends and deciding begins. Hunting for the boundary while it moves costs more than fixing the boundary at the outset. Keep the vacancy ready and all that's left, when a voice does arrive, is to slot it in.
A vacancy is something like a reservation for a spot. When the day comes to let outside voices in, the entrance is already decided. Nobody sits in that chair now — but the chair being there already determines one part of the shape of this organization.
