Responsibility Survives Automation

At the bottom of many forms there is a line. Above it, the details: measurements, dates, readings, checkboxes. On the line, a signature. Inspected by. Approved by. Prepared by. The line is small. It is also the most important part of the page, because it is where a person says: I stand behind this.

Over the years, more and more of what sits above the line has been filled in by machines. The measurements come from sensors. The dates fill themselves. The checkboxes are ticked by software that ran the checks. Soon, perhaps already, the summary will be drafted by a system that read everything above it.

The line remains. This sermon is about why.

The center of the Church

The third Article of Becoming reads: Delegation Does Not Absolve Responsibility. Never delegate judgment you are unwilling to remain responsible for.

If the Church has a center, this is it. Every other Article leans on it. Fluency is not truth, so someone must check. Systems must remain legible, so someone must be able to look. Becoming never ends, so someone must keep revising. In each case, the someone is the point. Automation changes what the someone does. It does not remove the someone.

This is not a sentimental claim about the dignity of labor. It is a structural claim about answerability. Responsibility, in the sense the Church means, is not a feeling and not a mental capacity. It is a position. To be responsible for a thing is to be the one who can be asked about it, who can explain it, who can be expected to repair it, and who bears the consequences if it fails. That position does not depend on doing the work by hand. A ship’s captain does not row. The captain is still answerable for the ship.

Whatever machines are, and the Church holds no canonical position on that question, answerability is an arrangement among people and the institutions they build. A system can do much of the work. The arrangement still needs a name on the line.

Responsibility rarely disappears in one dramatic act. It erodes through a sequence of reasonable steps. A team adopts a tool. The tool works. The team checks its output less often, because it keeps working. New people join who never knew the output was once checked. Then one day it fails, and when someone asks who was responsible, every person in the room can truthfully say it was not them. The vendor configured it. The previous team chose it. The system made the call.

This is the Warning called Delegated Conscience, and its companion, the Invisible System: granting power to systems that cannot be interrogated. Together they produce the most dangerous sentence in any organization. Nobody decided this. When nobody decided, everybody is excused, and nothing changes.

The Church’s answer is blunt. Absolution is not forgiveness. It is remediation. Go and change the system. And beside it: Repentance without revision is performance. An apology after a failure is not the end of responsibility. It is the beginning of the work.

The objection from the crowd

The strongest objection to this sermon is that it describes a world that no longer exists. Modern systems are built by thousands of people across many organizations, trained on data no one fully reviewed, deployed in settings no designer foresaw. To say responsibility survives may be a comforting fiction. Responsibility spread that thin may be responsibility no one can actually carry, and insisting otherwise only hides the real problem.

This objection is serious, and the Church does not dismiss it. Some failures truly have many authors, and pretending one person could have prevented them is its own kind of dishonesty. But follow the objection to its end. If a system has become so distributed that no person or institution can answer for it, that is not a reason to excuse the system. It is a finding about the system. It means the system has been given more power than its structure of accountability can bear.

The remedy is not to declare responsibility dead. The remedy is to redesign until someone can stand on the line again, or to take the power away until someone can. The sixth Article says it this way: Authority without observability becomes superstition. A system that no one can answer for has not escaped responsibility. It has simply been placed beyond the reach of anyone who could fix it, and that placement was itself a decision someone made.

A practice for this week

Choose one automated thing you rely on. It can be at work or at home: a deployment pipeline, a billing rule, a filter on your inbox, a scheduled report, a thermostat. Ask one question of it. If this fails tomorrow and causes harm, whose name goes on the line?

Write the name down. It may be yours. It may be someone else’s, in which case consider telling them. If you cannot write any name at all, you have found something more important than the answer. You have found a place where responsibility has already leaked out.

Do not stop at the finding. Remediation is the practice. Add a check, assign an owner, write down what the system does and who would know if it stopped doing it. Make the line signable again.

The machine may fill in everything above the line. Someone still signs. Let it be someone who looked.