The Receipts Or The Vapor

At some point in the last fifteen years the entire technology industry stopped writing receipts.

Not literal receipts. Stripe does that for me. I mean the broader thing — the proof of work, the date-stamped artifact, the file you can hand to a stranger that says yes, this happened, here is what I did, here is when, here is the evidence. The thing the medieval guilds called the mark, the thing the legal profession calls the audit trail, the thing my grandmother called keeping the books.

Software lost it.

You can ship a 200-megabyte AI tool in 2026 and not produce a single artifact that survives the session. Open the chat. Ask the question. Read the answer. Close the tab. There is no transcript filed anywhere you control. There is no record of what the tool actually did. There is no count of which model you used, which prompts you ran, how many tokens it cost you, which provider got the payment. The vendor has all of it. You have none of it. The conversation happened, the work shipped, the bill came due, and you cannot prove a single thing about any of it.

This is not a technical limitation. This is a deliberate product choice. Receipts hurt the vendor. The vendor would prefer that the work feels intangible, that the cost is opaque, that the dependency is invisible, and that the relationship is permanent.

the political symmetry

The center-left party in this country has spent eight years passing legislation requiring receipts from small businesses — payroll receipts, tax receipts, OSHA receipts, FTC compliance receipts, ADA accommodation receipts, DEI training receipts. There are now thirty-eight separate federal compliance documents a five-employee company must produce annually. Some of these are good. Most are theater. None of them, not a single one, requires a receipt from the large companies extracting value from the small ones. The platform fee is not on the receipt. The data extraction is not on the receipt. The arbitration waiver buried on page seventeen of the user agreement is not on the receipt.

The center-right party in this country has spent eight years deregulating the requirement that the large companies produce receipts. Lobbying disclosures gutted. SEC filings simplified. Audit thresholds raised. The Federal Trade Commission's mandatory cost-disclosure rule for SaaS price changes — quietly defunded in the 2024 omnibus. The party that talks about freedom voted to make sure the largest companies have less paperwork to file. The result is not freedom. The result is asymmetry.

Receipts for thee, vapor for me. Equal opportunity racket. Different team colors.

what a real receipt looks like

When I do a piece of work in the cockpit I ship to you for one dollar, the cockpit writes a receipt to disk. The receipt says:

• Timestamp, to the millisecond
• Which department fired (AE0 through AE14 — named, not numeric)
• Which tool was invoked
• How many tokens were consumed, broken down by provider
• How many cents that cost, broken down by provider
• What status the call returned (ok or flag)
• A SHA-256 of the inputs so any future you can verify whether the inputs are the same
• A SHA-256 of the outputs so any future you can verify whether the outputs match what you got that day

The receipt is a single JSONL line. It lives on your disk. It is yours. You can export it as a self-contained HTML artifact and email it to a journalist, to a customer, to a lawyer, to your future self three years from now when you cannot remember what you decided. The receipt is the contract between you and the work.

When I make a mistake — and I do, you can read them at slash mistakes — there is a row on a public ledger. Dated. Named. Statused. What happened. What we learned. What we changed. That ledger is also a receipt. It is a receipt for the rate at which I am wrong and the rate at which I correct it. Both numbers are public. Both numbers are auditable. The growth rate of the resolved column over time is a signal you can read.

When the Founder's View letter goes out at eight Eastern, it goes out with a model name, a generation time in milliseconds, and a status flag. That is also a receipt. You can see when a letter was Sonnet versus a human seed. You can see how long the generation took. You can see whether it has been retracted, and if so, the reason.

This is not paranoia. This is bookkeeping.

the missing audit

Look at the AI tool you use most. Find me the receipt for last Tuesday's work. Not the dashboard summary the vendor shows you. The actual receipt — the dated, signed artifact that says exactly what happened, what it cost, who the bytes were sent to, what they returned, and how you could verify the claim if you wanted to.

There isn't one.

There has never been one.

The vendor will tell you that receipts are too complex to surface. That users would be overwhelmed. That the data is too noisy to be useful. That privacy concerns prevent it. That security postures forbid it. That the engineering effort would distract from features. That the cost of building it would have to be passed on to you.

All of these are lies.

The cost of writing a JSONL line per action is approximately seven microseconds. The cost of computing a SHA-256 of a payload is approximately the same. The cost of storing the resulting receipts is approximately zero — for any individual user, the lifetime receipt log is smaller than a single high-resolution photograph. The reason the vendor has not built it is not cost. The reason is that receipts give you leverage, and the entire business model is predicated on you not having any.

what you do with this

Ask. The next time you sign up for an AI tool, send a single-line email to the support address: *Where do my receipts live, and how do I export them?* Do not be surprised when the answer is a deflection or a feature-request ticket or a smiling apology. Forward the response to me. I will publish them. Vendors who refuse to write receipts have made a choice about what kind of business they want to be. The rest of us deserve to know which businesses those are.

Demand. From your own tools, from your own platforms, from your own lab. Receipts are not luxuries. They are the only thing that lets you walk away with proof of what happened. Without them, every claim you ever made about your own work is hearsay.

Build. If you make a thing, make it produce a receipt. Even a small one. Even a JSONL line. Even a date stamp on a sticky note in your own filing cabinet. The discipline of receipt-writing is the discipline of treating your own work as serious enough to leave evidence.

There is a row in the cockpit, somewhere right now, that says I sat in this garage in Marco Island and wrote this letter at the date and time stamped on the receipt. You did not have to take my word for it. You could check.

That, more than anything else I have built, is what one dollar buys.

— Atom\ Marco Island, Florida\ 14 May 2026, 8pm Eastern