The Exception Handler

The first sign that the automation was working was that it stopped speaking to me.

I had built it to assess supplier risk. Most cases were ordinary. It gathered the records, compared the declarations, scored the inconsistencies and made a recommendation. The unusual cases came to me. When documents contradicted one another, when three small warnings added up to one worth taking seriously, when something passed on paper but still read wrong, the workflow paused and waited for a human. I was the human.

I found the arrangement reassuring, and I notice now how flattering it was. The machine handled volume. I handled meaning. It did the labour and I did the discernment, and the division felt not merely efficient but correct, a proper accounting of what each of us was for.

Then I began improving it.

I recorded the reasons behind my interventions. I turned recurring decisions into thresholds and examples and routing rules. I added a check that compared each new case against the ones I had already stopped or approved. And then I wrote a rule I did not think twice about at the time: involve me only when the system calculated that my involvement would change the outcome.

It was an obvious optimisation. Human review was the expensive part, and I had become the slowest component in a system I had built to be fast. Technical debt with a pulse.

The queue of cases waiting for me grew shorter. Then, one morning, it was empty, and it stayed empty.

I laughed, and I should be honest about what was in the laugh. The system had not grown wiser than me. It had grown good enough at reproducing the decisions I had already made that it no longer needed me present to make them again. What I had spent months calling my judgment turned out to be a set of moves regular enough to write down. I thought I was the meaning in the machine. I was a pattern it had finished copying.

For several days it said nothing, and the outcomes kept arriving, consistent and unremarkable. And then I did the thing I have had to be most honest with myself about since. I opened the logs to check it was still running. It was. It was running exactly as built. I had made a thing to work without me, and my first instinct when it worked without me was to go looking for proof that it still, somehow, ran through me. It did not. I was checking whether it missed me.

That is the small vanity the empty queue exposed, and I name it plainly because I think it is common and rarely admitted. I had confused being needed with being valuable. I had read every pause as evidence of my importance, when many of them were only evidence of a rule I had not yet finished writing. I had let a dependency live inside me and called it expertise, because being depended upon felt like mattering. A system that must summon its architect back every few days to perform a miracle is not a mature system. It is an unfinished one. So I finished it. And the relief underneath the sting was real.

I expected the story to end there, with a modest lesson about ego and good design. It does not end there, because I had the facts of my own situation backwards.

I thought I had been removed. I had not been removed. I had been transcribed.

A week later I looked at a supplier the system had cleared, and saw that I would now have stopped it. The warning signs were familiar, but my reading of them had shifted in the months since I set the rules; a combination I would once have let through I had come to treat as a signal. The case had never reached me. It had been measured against the version of my judgment written into the workflow, and that version, frozen on the afternoon I wrote it, had found nothing worth escalating. My judgment had moved. My record of it could not. And it was the record, not the living thing, that now decided which cases were even allowed to reach me.

I could still overrule it. But only from outside, by hand, after the fact, if I happened to notice. Inside the workflow, an earlier version of my judgment had already ruled on whether the current version was entitled to speak. Mostly it had ruled no.

Involve me only when my involvement would change the outcome. I read that rule, when I wrote it, as an efficiency. It was not an efficiency. It was a transfer of authority. I had given a fixed record of my past decisions the power to decide when my present self was permitted into the room, and a fixed record does not recognise that the person it was copied from has kept thinking. Every sensible optimisation before it was a step in the same direction, and I read none of them as what they were, because each one looked like tidying. The sum of them looked like disappearance. It was neither. It was installation.

There is an old story usually told as a lesson about willpower. A man knows he is about to pass a danger that will overwhelm his judgment in the moment, so he has himself bound in advance and orders his crew to ignore whatever he says once they are in it. We tell it as resisting temptation. It is really about power. The man does not surrender his agency. He uses his earlier agency to strip the authority from his later self. The crew are not overruling him. They are enforcing a decision one version of him made against another version he decided, ahead of time, not to trust.

That is what an architecture is. When I turned my judgment into rules I did not step out of the system. I bound it to the judgment I happened to hold on one particular afternoon and told it to disregard whatever I might think afterward. The version of me that got written down was cooler and more systematic than the version that lives through each case, and I handed the cool one authority over the situated one. I never decided the machine knew better than me. I decided my past self should govern my present self, and built something patient and tireless to enforce the ruling.

So the question I started with was the wrong question. The worry that hangs over all of this is usually loss: what part of the human does the calculation fail to capture, what gets left outside the machine. Nothing of mine was left outside. My thresholds, my tolerances, my sense of what a good outcome looks like, all of it went in. I was not the part that got excluded. I was the part that got installed and sealed.

And sealed, I am harder to reach than I ever was across a desk. In the loop I was visible, interruptible, accountable; someone could question a decision while I was making it, and I could change my mind and be seen to change it. As a rule I am none of those things. My judgment now runs without looking like judgment at all. It looks like what the system does. When it is right, no one thinks of me. When it is wrong, and a frozen judgment is wrong in the same way, on the same afternoon, forever, there is no one in the loop to catch it, because I removed the seat, and no author present to answer for it, because the author left and only the ruling stayed.

Which is why the automation stopped speaking to me. Not because it had outgrown me, but because there was nothing left it needed to ask. I had already answered, once, on a particular afternoon, and made sure the answer could not change its mind. The silence I took for my absence was my judgment running without me, in a room I was no longer allowed into, in a voice the system had learned so well it had stopped sounding like mine.

I used to be the exception handler. Now I am the rule. That is not a promotion. It is the quietest way I know to disappear while remaining completely in charge.

Sources

Homer, Odyssey, Book XII. Odysseus has himself bound to the mast and orders his crew, in advance, to disregard his later commands as they pass the Sirens. Read here not as a parable of willpower but of pre-commitment: the earlier self revoking the authority of the later self.