Consent is not a record
A checkbox manufactures permission, not accountability. Consent authorizes a decision; it does not account for how the decision was made.
There is a sentence institutions reach for whenever a decision they made comes under question, and it has the shape of an answer without the substance of one: you agreed to this. You clicked the box. You signed the form. You accepted the terms. The sentence is meant to end the conversation, and it usually does, because it sounds like it settles the matter of responsibility. But look at what it actually establishes. It establishes that you permitted the institution to act. It says nothing whatever about how the institution then acted, whether it acted well, or whether what it did to you can be defended on its merits. Consent and accountability are doing two completely different jobs, and we have let the first quietly stand in for the second.
Permission and account are not the same category. Permission is something you give in advance: a grant of authority to proceed. An account is something owed afterward: a defensible explanation of what was done with that authority. The grant tells you the action was allowed to happen. It tells you nothing about whether the action was right, whether it followed the rules it was bound by, or whether the same inputs would produce the same result if anyone bothered to check. A signature at the top of the relationship cannot answer questions that only arise at the bottom of it.
Yet the substitution has become a load-bearing feature of how organizations manage their exposure. The consent is collected at the moment of maximum leverage — when you need the service, the loan, the account, the care — and it is then deployed at the moment of maximum vulnerability, when something has gone wrong and you want to know why. The function of the checkbox was never really to inform you. It was to manufacture, in advance, the institution's defense against having to account for itself later.
You consented to be subject to the decision. You did not consent to never being told how it was made. Those are different agreements, and only one of them was on the screen.
What consent cannot do
Consent cannot carry the evidence a decision rested on. When you agreed to terms, you agreed to a process in the abstract — to the idea that a determination would be made about you according to some criteria. You did not, and could not, agree to the specific facts that would later be assembled about you, the order they would be weighed in, or the sources they would be drawn from. Those did not exist yet. So consent, by its nature, is blind to the very thing a record exists to expose. It is a permission granted over a process whose particulars are unknowable at the moment of granting.
Consent cannot freeze the rules that were active when the decision landed. The terms you accepted almost always reserve the right to change the terms. The policy that governed your case may have been written after you clicked, and amended again after the decision, and there is nothing in your agreement that pins down which version was in force when it counted. Consent is a signature on a document that explicitly permits itself to be rewritten. As an authorization that is convenient for the institution. As a record it is worthless, because a record's entire value is that it cannot be changed after the fact, and consent is built to be changed after the fact.
And consent cannot be replayed. You cannot feed a checkbox back through a process and watch where the decision lands, because the checkbox contains no inputs and no logic — only the fact that you assented to be subject to whatever the inputs and logic turned out to be. The thing that would let you contest the outcome is precisely the thing consent does not contain. This is the heart of the confusion: people treat the agreement as though it documented the decision, when all it documented was their willingness to live with a decision they had not yet seen.
Where the substitution does its damage
The danger is not that consent exists. Consent is legitimate and often necessary; some things genuinely should not be done to a person without their permission. The danger is the substitution — institutions reaching for consent exactly where they owe a record, and being allowed to treat the first as discharge of the second. An authorization to act is being accepted as an account of how one acted, and the two are separated by everything that matters: the evidence, the rules, the reproducibility, the whole apparatus that lets a determination be checked rather than merely permitted.
You can see the maneuver most clearly in its timing. Notice that consent is always invoked retrospectively, as a shield, and never offered prospectively, as a record. No institution responds to "show me how this decision was made" by producing the consent form, because everyone understands, at some level, that the consent form does not show how the decision was made. It shows that you let them make it. When the question is how, pointing at the whether-you-allowed-it is a change of subject dressed as a reply.
So the discipline is simply to refuse the substitution, out loud, every time it is attempted. When an institution answers a question about its conduct by reminding you what you agreed to, the correct response is that the two are not the same and both are owed. Yes, I authorized you to decide. Now account for how you decided. A Decision Receipt that carries the real evidence and the frozen rules and enough state to replay the outcome is an account. A signature collected at the door is a permission slip. An institution that offers the second when you have asked for the first has not answered you. It has hoped you would not notice the difference — and the whole point of asking twice is to make clear that you have.
— 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.