Who gets to see the reasons

We talk about transparency as though it were a property of documents — as though a decision becomes transparent the moment its reasons are written down somewhere. This is the mistake that lets an institution be perfectly transparent and perfectly opaque at once. The reasons exist. They are complete, honest, well-kept. And no one who was affected by the decision can get to them, read them, or understand them. The document is transparent to a filing cabinet. It is opaque to the only person it was supposed to serve. Transparency, I want to argue, is not a feature of the record. It is a relationship between the record and an audience with standing to read it.

Standing is a word worth pausing on, because it carries the whole idea. To have standing is to be recognized as someone entitled to ask — to be the kind of party whose question the system is obligated to answer, not merely permitted to ignore. A record that answers no one in particular answers no one at all. And the audience that matters is not the general public, and not the institution's own auditors, though both may have their claims. The audience that matters first is the person the decision was about. They have the strongest standing there is: it happened to them.

Once you see transparency as a relationship rather than a document, a whole class of hollow gestures becomes legible. The privacy policy no one can parse is not transparent; it is disclosed. The reasons available only on written request, adjudicated by the same body that made the decision, are not transparent; they are gated. The dashboard that shows the outcome but not the reasoning behind it is not transparent; it is a window onto a wall.

A reason kept where the affected party cannot reach it is not a reason given. It is a reason retained, which is closer to a secret than to an explanation.

The three failures of standing

There are three ways a record can hold the reasons and still fail to make them transparent, and it is worth naming each because they are usually confused for one another. The first is reachability. The reasons exist but the affected party has no route to them — no request they can file, no portal they can open, no clerk obligated to respond. The record is real and the door is locked. This is the failure institutions find most convenient, because it requires them to do nothing dishonest; they simply never build the door, and point, when asked, at the reasons safely inside.

The second is legibility. The party can reach the reasons but cannot read them — they arrive as a model's raw output, a policy citation with no policy attached, a confidence figure with no account of what it measured. Reachability without legibility is a cruelty dressed as compliance: here are your reasons, in a form you cannot use, and now we have discharged our duty. A record has to carry not only the evidence and the rules but the rules as they can be understood by the person bound by them, or it has handed over a locked box and called it an open one.

The third is standing to contest, which is the deepest of the three. Even reachable, legible reasons are not fully transparent if the party can read them but can do nothing with what they read — if there is no path from I see why you decided this to and here is where you were wrong. Transparency that stops at reading is a courtesy. Transparency that enables contest is accountability. The reasons are shown not so the party can admire them but so the party can fight them, and a record built for reading but not for rebuttal has confused the two.

Building the record for its reader

A Decision Receipt takes the reader as a design constraint, not an afterthought. It is built so the person the decision was about can reach it, read it in terms they are bound by, and use it to contest — carrying the evidence that was actually consulted, the rules as they stood, and enough state to replay, all pointed at an audience with standing. The receipt is not the institution's private memory of what it did. It is the affected party's copy of the reasons, held in a form they can act on. Provenance without an audience is archaeology. Provenance handed to someone with standing is accountability.

This reframes the design question in a useful way. The question is not have we recorded our reasons — nearly everyone can say yes to that. The question is who, specifically, can see them, and what can that person do once they have. Name the audience. If the honest answer is that the reasons are complete and legible and reach exactly no one with a stake in the decision, then the institution has built a magnificent record of things it will never have to answer for.

So the next time you are told a system is transparent, do not ask to see the document. Ask a sharper question: transparent to whom, reachable by whom, contestable by whom. If the answer to all three is the affected party, you are looking at accountability. If the answer is an auditor who will never come, a regulator with no route in, or a filing cabinet, you are looking at a record that has confused being written down with being answerable. Only one of those is transparency, and it is the one that names its reader.

— Dispatches · Summit Cognitive