A crowd cannot receive an appeal
Automated systems decide about people at the scale of crowds, but accountability is owed at the scale of the person.
There is a sleight of hand at the heart of how large systems defend themselves, and it works by quietly changing the subject. You come to an institution with a complaint about a decision that landed on you — a denial, a flag, a refusal — and the answer you receive is about someone else. It is about the population. The system is accurate across the whole. The policy is fair in the aggregate. The error rate is within tolerance. All of this may be perfectly true, and none of it is responsive to what you asked, because you did not ask about the population. You asked about yourself. The institution decided at the scale of the crowd and is now trying to be accountable at the same scale, and those scales do not match.
The mismatch is not a technicality; it is the whole moral problem of automated decision-making compressed into a single move. Justice is owed to persons. A person is not a statistic and cannot be answered with one. When a system that is right ninety-nine times out of a hundred lands wrong on you, the ninety-nine correct decisions are no comfort and no defense — you are the hundredth, and the decision that governs your life is the one that was wrong. A policy can be fair to the population and unjust to the individual it happens to fall on, and these are not in contradiction, because they are claims about different things. The aggregate is true. It is simply not about you.
And here is the trap the individual falls into. In a decision made about a million people at once, the individual has no natural standing. There is no moment, no room, no file that is theirs. They are one row in a table, one case in a batch that was processed as a batch and never as a case. To object, they first have to be extractable from the crowd — to be able to say, of all these million decisions, this one, mine, is the one I am contesting, and here is what it rested on. Without that, the complaint has nowhere to attach. It slides off the aggregate and dissolves.
A system can be fair to a million people and unjust to one of them, and the one it wronged has no standing to say so — unless the record kept their single case intact.
The crowd has no grievance; only a person does
It helps to notice that the aggregate cannot actually be wronged. A population does not have a case; it has a distribution. Only a person has a grievance, because only a person has the singular fact — I was denied, I was flagged, I was refused — that a grievance is made of. This is why an institution that can only speak in aggregates is, in a precise sense, unable to answer a complaint at all. It can describe how the system behaves across everyone. It cannot address what the system did to anyone. The gap between those two is exactly the space where injustice lives unexamined, because the injustice is always individual and the defense is always collective, and they never meet.
Automation widens this gap rather than closing it, and does so almost invisibly. A human clerk deciding one case at a time produced, as a byproduct, a per-person artifact — a file, a note, a decision attached to a name. The individuality of the decision was built into the medium. A system deciding a million cases in an afternoon produces, by default, an aggregate outcome and a set of overwritten states, and the per-person thread is exactly the thing that gets optimized away because retaining it was never the objective. The scale that makes the system efficient is the same scale that dissolves the individual case into the mass. Efficiency and standing are pulling in opposite directions, and left alone, efficiency wins.
To be accountable at scale is to keep the individual thread
The resolution is not to slow the system down to human pace, which no one will do and which would help no one. It is to insist that scale in the decision does not require scale in the accountability — that a system can decide about a million people at once and still owe each of them a record of their own. This is what a Decision Receipt does that an aggregate report cannot: it preserves, for the single person, the inputs their decision actually rested on, the rule in force when it was made, and enough state to replay it. The million decisions can be made as a batch. The million records are individual, one per person, each a thread that leads from the mass back to a single case.
That thread is what restores standing. With it, the person who was wronged is no longer arguing against a distribution they cannot dent. They can extract their case from the crowd, point to the specific inputs and the specific rule, and contest the decision that was actually made about them rather than the average of decisions made about everyone. The institution's aggregate accuracy becomes irrelevant to their complaint, as it should be, because the complaint was never about the aggregate. And the institution, for its part, can answer at the level the person is owed — not by reciting its error rate, but by producing the one decision under dispute and defending or repairing it on its own terms.
So the test of whether a system is accountable at scale is not how good its aggregate numbers are. A system can have excellent numbers and owe nothing to anyone, because good numbers are a fact about the crowd and accountability is a debt to the person. The test is whether, for any single individual in the million, the system can still produce their decision — intact, contestable, theirs. To decide at the scale of the crowd is unavoidable and often fine. To be accountable at the scale of the crowd is a category error. Accountability is owed one person at a time, and the record is what keeps each person's case from vanishing into the number that describes them all.
— 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.