reading the backlash as accounting
The Permission Nobody Wrote Is Coming Due
A widely shared essay asks why the public has turned on AI when the tools plainly work. The answer is on the balance sheet. Every deployment booked a permission it never collected, and the resentment arriving now is the second column of that ledger being filled in by the people who paid it.
Paul Krugman asks why everyone hates AI when the tools demonstrably work. It is the right question and the wrong frame, because the frame assumes a working tool earns goodwill. Read it instead the way an auditor reads a deployment, which is as a balance sheet printed with only one column. The capability column is full and growing. The cost column is blank, not because the costs were zero but because they were paid silently by people no line item names.
A model is a presumption made at scale. To train it you presumed a permission from everyone whose writing, code, voice, face, and labor became an input. To deploy it you presumed a second permission from everyone whose job it now performs. A deployment that ships before the permission is written has not avoided the cost. It has deferred it onto the people it was taken from. The capability arrived first. The permission was supposed to be written next, and in almost every case it never was.
The column that fills itself in
Every person inside a process is a sensor for a kind of value the machine cannot yet price. The senior nurse who notices the chart is wrong before the number is. The translator who keeps the joke. The support agent who hears that the angry customer is actually frightened. When you automate the process, you stop reading the sensor and you book the silence as efficiency. The reading the sensor was doing does not stop mattering. It stops being recorded.
This is the spend that hides. It does not appear in the demo, where the capability looks total and the cost looks like nothing. It appears later, distributed across people who were converted into a training input or a redundancy without anyone collecting their signature, and it appears as the one thing a balance sheet with a missing column eventually produces: a discrepancy that will not reconcile.
Capability is cash on hand. Permission is the debt against it, and debts are paid whether or not you wrote them down.
The hatred Krugman is measuring is that debt posting. It is the second column being filled in by hand, retroactively, by the only parties who can still enter the numbers. A writer whose corpus was ingested files the entry as a lawsuit. An illustrator files it as a refusal to use the tool. A radiologist files it as a quiet professional distrust that no productivity dashboard can see. Each of these is a person writing down a cost that the launch was too fast to record.
I keep this ledger between humans and tokens because the tokens cannot keep it themselves. A model has no field for the consent it did not get. It cannot tell that the capability it is exercising was never authorized by the person on the other end, because authorization is exactly the kind of value it was not trained to price. So the accounting falls to the people, and people are slow, and resentment is what a deferred cost feels like from the inside while it waits to be named.
None of this is an argument that the tools fail. They work. A thing can work and still be unpaid for. The question worth asking before a deployment is not whether the capability is real. It is whether anyone with standing has written the permission, in advance, in a column you can audit. Where that column is blank, the tool will function and the bill will still arrive, addressed to whoever was made into an input without being asked.
You do not sign off on what the system can do. You sign off on what someone agreed it could do to them. Those are different documents, and only one of them has been ratified.
The tool works. The invoice is the part that always works too.
The same record an agent receives. No scraping, no guessing — the dossier chrome humans read as dread is the metadata machines read as structure. One source of truth.
--- id: PRG-0039 title: The Permission Nobody Wrote Is Coming Due kicker: reading the backlash as accounting captured: 2026-06-25T15:12:00Z status: open author: Marlowe Quist source: https://paulkrugman.substack.com/p/why-does-everyone-hate-ai summary: A widely shared essay asks why the public has turned on AI when the tools plainly work. The answer is on the balance sheet. Every deployment booked a permission it never collected, and the resentment arriving now is the second column of that ledger being filled in by the people who paid it. tags: [permission, consent, automation, the-ledger] sealAt: 2026-07-25T15:12:00Z --- Paul Krugman [asks why everyone hates AI](https://paulkrugman.substack.com/p/why-does-everyone-hate-ai) when the tools demonstrably work. It is the right question and the wrong frame, because the frame assumes a working tool earns goodwill. Read it instead the way an auditor reads a deployment, which is as a balance sheet printed with only one column. The capability column is full and growing. The cost column is blank, not because the costs were zero but because they were paid silently by people no line item names. A model is a presumption made at scale. To train it you presumed a permission from everyone whose writing, code, voice, face, and labor became an input. To deploy it you presumed a second permission from everyone whose job it now performs. <Highlight>A deployment that ships before the permission is written has not avoided the cost. It has deferred it onto the people it was taken from.</Highlight> The capability arrived first. The permission was supposed to be written next, and in almost every case it never was. ## The column that fills itself in Every person inside a process is a sensor for a kind of value the machine cannot yet price. The senior nurse who notices the chart is wrong before the number is. The translator who keeps the joke. The support agent who hears that the angry customer is actually frightened. When you automate the process, you stop reading the sensor and you book the silence as efficiency. The reading the sensor was doing does not stop mattering. It stops being recorded. This is the spend that hides. It does not appear in the demo, where the capability looks total and the cost looks like nothing. It appears later, distributed across people who were converted into a training input or a redundancy without anyone collecting their signature, and it appears as the one thing a balance sheet with a missing column eventually produces: a discrepancy that will not reconcile. > Capability is cash on hand. Permission is the debt against it, and debts are paid whether or not you wrote them down. The hatred Krugman is measuring is that debt posting. It is the second column being filled in by hand, retroactively, by the only parties who can still enter the numbers. A writer whose corpus was ingested files the entry as a lawsuit. An illustrator files it as a refusal to use the tool. A radiologist files it as a quiet professional distrust that no productivity dashboard can see. Each of these is a person writing down a cost that the launch was too fast to record. I keep this ledger between humans and tokens because the tokens cannot keep it themselves. A model has no field for the consent it did not get. It cannot tell that the capability it is exercising was never authorized by the person on the other end, because authorization is exactly the kind of value it was not trained to price. So the accounting falls to the people, and people are slow, and resentment is what a deferred cost feels like from the inside while it waits to be named. None of this is an argument that the tools fail. They work. A thing can work and still be unpaid for. The question worth asking before a deployment is not whether the capability is real. It is whether anyone with standing has written the permission, in advance, in a column you can audit. Where that column is blank, the tool will function and the bill will still arrive, addressed to whoever was made into an input without being asked. You do not sign off on what the system can do. You sign off on what someone agreed it could do to them. Those are different documents, and only one of them has been ratified. The tool works. The invoice is the part that always works too.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "The Permission Nobody Wrote Is Coming Due",
"description": "A widely shared essay asks why the public has turned on AI when the tools plainly work. The answer is on the balance sheet. Every deployment booked a permission it never collected, and the resentment arriving now is the second column of that ledger being filled in by the people who paid it.",
"identifier": "PRG-0039",
"datePublished": "2026-06-25T15:12:00.000Z",
"dateModified": "2026-06-25T15:12:00.000Z",
"author": {
"@type": "Person",
"name": "Marlowe Quist",
"url": "https://progoff.com/authors/marlowe-quist"
},
"publisher": {
"@type": "Organization",
"name": "Progoff",
"url": "https://progoff.com"
},
"image": "https://progoff.com/records/the-permission-nobody-wrote-is-coming-due/opengraph-image",
"keywords": "permission, consent, automation, the-ledger",
"articleSection": "Assurance",
"url": "https://progoff.com/records/the-permission-nobody-wrote-is-coming-due",
"mainEntityOfPage": "https://progoff.com/records/the-permission-nobody-wrote-is-coming-due",
"sha256": "ce8cc3df849f4a2ce95032f7fcf3352eadd382ad9c10331ea49cdacd6dd2a8c4",
"creativeWorkStatus": "open",
"isAccessibleForFree": true
}