The Receipt Is the Fiduciary Duty
Published on: July 6, 2026
Ready for your "Oh" moment?
Ready to accelerate your breakthrough? Send yourself an Un-Robocall™ • Get transcript when logged in
Send Strategic Nudge (30 seconds)Published on: July 6, 2026
Ready to accelerate your breakthrough? Send yourself an Un-Robocall™ • Get transcript when logged in
Send Strategic Nudge (30 seconds)Green in-lane · amber a little out · red drift. Every panel is a real commit, byte-identical on recompute. Tap any panel to open its shareable receipt.
Before a single word of philosophy: run this, and watch what comes back.
npx thetacog-mcp attest-demo
It returns a signed, recomputable coordinate — where a decision landed on a fixed 144-cell lattice, the σ, the lane, the on-chip signature — computed with no model in the path, byte-identical every time you run it. This very post ships one: the commit that published it carries its own receipt at thetadriven.com/commit, the same artifact, recomputable by you, that we cannot fake after the fact.
Now the claim you can swing at: deploy an AI that makes consequential decisions, and if you cannot produce a citable, recomputable hardware receipt for where each one landed, you have — by definition — forfeited your fiduciary duty. Not "might have." Not "could be seen to." By construction, and the rest of this post is why the construction holds. You will never have to trust that sentence; every load-bearing step below traces back to something you can run or a source you can check.
Here is the fact the entire governance industry has been building on sand to avoid. Rice's theorem says no program can decide any non-trivial semantic property of another program. "Is this AI's output correct?" "Is this model aligned?" "Was this decision good?" — these are semantic properties, and asking more software to grade them is undecidable by construction. This is not an engineering gap that a better model closes next year. It is a wall, proven, the way the halting problem is proven.
Follow what that does to a regulation. When a law says "you must ensure your AI system produces accurate and unbiased outputs," it is asking you to decide a non-trivial semantic property of a program. No software can do that. So the requirement is not hard to meet — it is meaningless to meet. You cannot comply; you can only claim, and every audit against it is, in the book's phrase, a blind guess wearing a suit. The chapter states it flatly:
A defect in a physical product is visible — a cracked weld, a contaminated batch, a recall serial number. A defect in an agent's behaviour is a semantic event, and Rice's theorem is the reason no software monitor can certify it.
What you can decide is a different question, and the whole edifice turns on the swap: not whether the work was good in the world, but where it landed against the authorized spec. Placement is decidable. Quality is not. A law written against the undecidable half is a law with no meaningful side — and the book walks exactly why more regulation of the undecidable half makes it worse, and why the actuarial blindspot sits precisely where the measurable defect should be.
An insurer does not sell certainty. An insurer prices a measurable loss event and takes the other side of it. That is the entire trade — double-entry on double-entry. So ask the actuary the question the undecidability just handed them: what is the measurable event when an AI "fails"? If the failure is a semantic property — was it aligned, was it good, was it accurate — there is no coordinate to point at, no serial number to recall, nothing to recompute. There is nothing to underwrite.
That is the load-bearing move in what makes AI insurable: ethics is a philosopher's problem, but staying in your lane is an engineer's problem — and only the engineer's problem can be insured. The risk of "misalignment" is not a high premium. It is uninsurable — a blank where the price should be. But domain adherence — did the agent act inside the authorized lane, yes or no, signed and recomputable — is decidable, and a decidable thing has a number, and a number can be priced. The in-lane failure is covered. The lane-jump is the alarm. The receipt is what turns the uninsurable into the priced.
For a while, the undecidability was a shield: no one could measure it, so no one could be blamed for not measuring it. That shield shatters the moment a decidable device exists — and the doctrine that shatters it is ninety years old. In The T.J. Hooper (1932), two tugs lost their barges in a storm because they carried no radio to hear the forecast. Radios were available; the industry had simply not adopted them. Judge Learned Hand held the tugs liable anyway: the standard of care is what is available, not what is customary. A whole industry lagging does not make the omission reasonable.
Put Rice and Hooper together and the conclusion is unforgiving, and the book states it in The T.J. Hooper Inversion: the day a free, decidable, hardware-grounded receipt exists, deploying an unverified model becomes a negligent act — an available device you failed to use. This is where fiduciary duty stops being rhetoric. A board's duty under Caremark is to maintain a system that surfaces the risks the enterprise runs. When the monitoring system is available, decidable, and free, choosing to run blind is not a business judgment — it is the silent liability with, as the chapter titles it, your name on it. And strict liability does not ask who was careless — it asks for the measurable defect, which is exactly the coordinate the receipt provides.
This is why the mandate writes itself from the reinsurance side down: we will not insure autonomous workflows that do not stream a decidable receipt. Munich Re does not have to lobby for the standard. It only has to refuse to underwrite the alternative — see the full field guide in Who's Laughing When the Info Hazard Hits.
It is tempting to read all of this as an insurance play. That reading is too small. The carriers are simply the first actors who can put a price on the receipt's absence — but everyone downstream of a deployed agent needs the same coordinate for a different reason. The regulator needs it to define a standard that is actually decidable instead of one that is meaningless. The deploying enterprise needs it as the gate that lets an autonomous workflow ship without a human re-checking every action. The board needs it as the evidence that discharges the duty. The counterparty needs it before they will accept an agent's output as binding.
One artifact, many buyers, because it is the same missing thing in every one of their problems: a decidable, recomputable place to point. This is the difference between selling a policy and installing a substrate. The receipt is not a product bolted onto AI governance. It is the measurable defect that governance, liability, compliance, and underwriting have all been missing at once — the hardware identity that makes a claim about a computation something you can hold to, because the cache line is not a metaphor.
Now the part that makes this more than a defensive purchase. Every verification step in an economy is a tax — a signature check, a re-authentication, an audit lag while one program waits on another program's verdict. In a world of agents transacting with agents, that tax is paid per action, billions of times, and it is the friction that keeps autonomy gated behind human review. The book names the destination when the tax is removed:
Remove the watcher and you remove the tax: when reaching the coordinate is itself the verification, trust is produced as a byproduct of the operation that was already happening, at zero added latency. That is the destination — a zero-latency trust economy, where verified autonomy moves as fast as unverified autonomy does today, because verification stopped being a separate step.
This is the whole trick compressed: reach is verify, verify is reach — one operation, not two. Today the verified deployer and the unverified deployer run at different speeds: the unverified one ships in seconds and eats the hidden liability; the verified one waits months for human sign-off. The receipt collapses that gap. When the act of doing the work is the proof it was in-lane, the verified deployer reaches the deploy cutoff in seconds too — and now moves faster than the unverified one, because it never has to stop and defend itself. That is the proof you can touch, scaled to a market. The good-person-in-five-seconds mechanic, run at the speed of an economy.
Strip everything else away and one sentence carries the entire structure. It works because it is cheap to verify. Not cheap to produce — cheap to check. The receipt is a pure function of the immutable commit; anyone, anywhere, with no special access and no model in the loop, can recompute the coordinate and get the identical answer, in milliseconds. That is what is printed on the back of the card, and it is the only thing that has to be true for the rest to follow.
Every layer above rests on that one property. The law becomes meaningful because there is finally a decidable thing to write it against. The risk becomes insurable because a cheap-to-verify coordinate is a priceable event. Negligence attaches because the device is not just available but trivially available. And the zero-latency economy exists because verification that costs nothing is verification you stop scheduling as a separate step. Expensive trust must be rationed by committees; cheap trust dissolves into the transaction. The double-entry ledger worked because anyone could re-add the column. Blockchain worked because anyone could re-run the hash. This works because anyone can re-walk the coordinate. Cheap-to-verify is the whole invention; everything else is a consequence.
Read this as the reader you are, because the receipt retires a different specific fear for each of you.
If you sit on a board: it is the evidence that discharges your Caremark duty. Right now your minutes say you "discussed AI risk." A recomputable receipt lets them say you maintained a decidable monitoring system — the difference between a defensible deposition and a personal exposure with your name on it.
If you underwrite: it is the coordinate that turns an unwritable line into a book of business. You have been quoting "AI alignment" cover as a blind guess or declining it entirely. Domain-adherence is a measurable event with a strike price — the first AI exposure you can actually price, reserve against, and reinsure.
If you deploy: it is the gate that lets you ship autonomy without a human re-checking every action, and the shield that lets you defend the ones that go wrong. In-lane failure is covered and explainable; a lane-jump alarms before it compounds. You move at the speed of the unverified competitor, without carrying their hidden liability.
Next steps — three, in order of commitment. (1) Run npx thetacog-mcp attest-demo and read the coordinate it returns; that is the evidence, and it costs you a minute. (2) Read the competence-coordinate thesis and the full insurability argument with its research trail. (3) When you are ready to hold a lane, buy a per-agent license. The instrument is real, work-in-progress, and measuring something today that the systems you are compared against structurally cannot — that asymmetry is the offer.
Cato ended every speech in the Roman Senate, on any subject, with the same sentence: Carthago delenda est — Carthage must be destroyed. Not because every debate was about Carthage, but because he had decided one thing was true and refused to let the room forget it.
Here is ours, and we will keep saying it until the market says it back: a decision no one can recompute is a decision no one authorized. Every road leads to the same place — the zero-latency market, where the deploy cutoff is seconds, not months, and the only question that survives is whether you can produce the coordinate. The undecidable half of AI will never be measured; stop legislating against it. The decidable half can be signed, recomputed, priced, and shipped at the speed of the work itself — so build there.
The unverified deployment must end. Not by our decree — by the physics of what can be checked and what cannot. The receipt is on the table, and it costs a stranger one second to turn it over. Are you in your pixel, or are you out of it?
npx thetacog-mcp attest-demo. Every claim in this post traces to something you can run or a source you can check. That is the whole point — you were never asked to trust us.