The paperwork of power
Bureaucracy's paperwork was an accidental accountability machine. Automation removes it — so the record now has to be designed in on purpose.
For most of the modern era we cursed the paperwork. It was the friction in every interaction with power: the form in triplicate, the file that had to be pulled, the memo that had to be initialed before anything could move. We built whole genres of complaint around it, and the complaints were not wrong — paperwork was slow, it was wasteful, it was often a way of saying no without having to take responsibility for saying no. But there is a thing the paperwork did, quietly and almost as a byproduct, that we never quite gave it credit for, and that we are only now noticing because it has begun to disappear. The paperwork left a record. Every consequential act, in passing through it, deposited a trace that someone could later find and read.
That record was not the point of the paperwork. Nobody designed the bureaucratic file as an accountability instrument; it was designed to route work, to assign responsibility, to make the next clerk's job possible. The accountability was incidental — a side effect of the fact that, in order to do anything at all, the institution had to write it down. To deny a claim, someone had to produce a written denial. To grant an exception, someone had to sign for it. To move a case forward, someone had to record where it stood. The reasons, the inputs, the names attached to the judgment: all of it accumulated in the file not because the institution wanted to be held to account but because the institution literally could not function without leaving these marks behind.
The record was a side effect, not a virtue
This matters enormously for understanding what automation is doing to us, because it means the accountability we enjoyed was free in a very specific and now-precarious sense. We did not pay for it deliberately. We got it as change from the transaction cost of doing things by hand. The file existed because the alternative — acting without writing anything down — was simply not available to a human institution operating at the speed of paper. You could not deny a benefit telepathically. The act and its record were welded together by the medium itself.
Automation breaks that weld. A system can now perform the consequential act — deny the claim, grant the exception, advance or halt the case — without producing any incidental record at all, because the medium no longer requires one. The whole point of automating a process is to strip out the friction, and the record was friction. So it goes. What is left behind is the act without its trace: a decision made, an effect delivered, and nothing in particular written down, because nothing needed to be written down for the machine to do its work. The accountability that used to fall out of the process as a matter of course now falls out of nothing. It has to be put back in deliberately, or it is simply gone.
The file was never meant to hold power to account. It did so only because power, in the age of paper, could not act without first writing itself down. Take away that necessity and the accountability leaves with it.
What used to come free now has to be built
This is the part that I think we have not fully absorbed. There is a widespread assumption that automated systems are, if anything, more transparent than the human bureaucracies they replace — after all, they are made of code and logs and data, and surely all of that constitutes a record. But a system log is not the file. The log records that the system ran; it does not record why this person received this outcome on this evidence under these rules. The thing the old file captured almost by accident — the substance of the judgment, in a form a person could later read and contest — is exactly the thing an automated process omits unless someone specifically builds it to keep that substance. Logs are abundant. Accounts are not. They are different objects, and the abundance of the first can disguise the absence of the second.
So the question for any institution that automates a consequential function is no longer whether to keep records — that decision used to make itself — but whether to reconstruct, on purpose, the accountability that the paperwork used to supply for free. This is what a Decision Receipt is for. It is the deliberate replacement of the incidental file: a record built not as a byproduct of acting but as a designed obligation, carrying the evidence the decision rested on, the rules that bound it, and enough state to let the affected party reconstruct and contest what was done. It exists because the act no longer produces it on its own, and someone decided the act should still be answerable.
There is a temptation to treat this as nostalgia for bureaucracy, and it is not. The paperwork deserved much of the scorn it got, and a great deal of it was pure friction protecting nobody. The point is narrower and harder. We benefited, without intending to, from a property of the old medium that the new medium does not share, and we have been spending that benefit down without replacing it. The accountability was a dividend of inefficiency, and we have spent the last generation, rightly in most respects, eliminating the inefficiency. What we have not done, in most places, is notice that the dividend went with it — and start paying for, on purpose, the thing we used to get as change.
— Dispatches · Summit Cognitive
Continue from here
Turn the argument into a practice.
Get new dispatches, assess how your organization handles consequential decisions, or explore Summit Cognitive.