There is a particular silence that settles over a legislative chamber when someone tells the people inside it that the machines have started checking themselves. It is not the silence of agreement. It is the silence of a room realizing, all at once, that the safety net everyone assumed was stretched beneath them was never tied to anything at all.
That was the texture of a New York City Council hearing, where a handful of former AI lab researchers testified to something that should have stopped traffic: humans are reviewing AI-built systems less often. Not by decree. Not after a decision. But because machine-generated output has quietly outrun the human capacity to inspect it, and the review step has degraded into a formality — a signature on a page, performed for the record rather than for the safety it supposedly guarantees.
I have spent my adult life listening to what the data refuses to say. This is one of those moments. The story is not the testimony. The story is the gap between the testimony and the evidence that should have accompanied it — the review rates never cited, the systems never named, the quantified harm never produced. Finding the signal in the silence of the bear taught me that the loudest part of any narrative is usually the part nobody says out loud. Policy is no different. And I cannot stop thinking about a municipal hearing on AI safety, because crypto has already built its entire quality culture on the exact assumption that just got called into question: that a human reads the code before it goes live.
Set the scene for readers who live on-chain and may have missed a governance story that has nothing, and everything, to do with us. New York City Council — not a federal agency, not the European Commission, but a city council — hosted former AI lab researchers who testified that human oversight of AI-generated and AI-built systems is declining. The framing was familiar to anyone who tracks AI safety discourse: supervision is weakening, accountability is diffusing, and regulation should intervene. Crypto Briefing, a blockchain outlet, carried the story. That detail matters. When a crypto publication starts running pure AI governance news, it usually means the two worlds are colliding faster than either side's institutions are prepared for.
The essential background is this. Over the past three years, the dominant workflow inside AI development has shifted. Models write code. Agents test it. Pipelines deploy it. The human role has migrated from producing the work to reviewing the work. And review, by its nature, is a bottleneck. It does not scale with the thing it reviews. If a system can generate a thousand pull requests an hour, you do not hire a thousand reviewers — you hire a policy, a checklist, and a hope. That is the structural trap, and it is not unique to AI labs. It is the same trap DeFi walked into the moment smart contracts became complex enough that no single person could hold the whole thing in their head.
Now hold that thought and walk it across the street into crypto, where we have been running a version of this experiment for a decade — and where the audit has become a ritual we perform so we can keep believing the code is safe.
I spent the 2021 cycle watching meme coins with no utility outperform projects with forty-page whitepapers, and I wrote then that hype had become the new utility. What I did not fully appreciate was that the same attention economy which made community cohesion more valuable than code was quietly devaluing the audit itself. An audit became a marketing line — a badge on a landing page, a logo next to a ticker. Decoding the hidden stories behind the tokenomics means reading the things the tokenomics page omits, and the thing it increasingly omits is the name of the human who actually read the contract. By 2022, in the wreckage of FTX, I was interviewing founders for a Substack I called The Skeleton Key, cataloguing which narratives survived the bear and which were ghost stories. The audit was one of the ghost stories. Everyone said they had one. Almost no one could explain what it had caught.
So when I read that former AI lab researchers told New York's council members that humans are checking AI-built systems less often, I did not read it as an AI story. I read it as a crypto story arriving three years late, wearing a different jacket. Because the crypto industry has already run the experiment. We have already discovered what happens when the volume of code outruns the volume of review. The answer is not that everything breaks. The answer is that the review becomes theater — and the market learns to price the theater as if it were the substance.
Let me be precise about the mechanism, because this is where the sentiment analysis matters more than the engineering. The human review step does not fail loudly. It fails quietly, through a psychological process that behavioral finance has documented for decades: automation bias. When a machine produces output, humans systematically overweight it. We assume the machine has already done the checking. Our attention drops. We skim. We approve. The reviewer who is asked to check a hundred AI-generated artifacts a day does not check a hundred; they check the first five and then pattern-match the rest. This is not laziness. It is the predictable behavior of a nervous system asked to do something the nervous system cannot do — sustain vigilance against a threat that never quite materializes.
I first quantified this instinct during DeFi Summer in 2020, when I scraped five thousand comments from r/ethereum and correlated gas-fee spikes with retail withdrawal rates. I was trying to prove that gas anxiety was a psychological barrier, not just a technical one. What I found was more general and more unsettling: the crowd did not react to the fee. The crowd reacted to the story about the fee. Narrative led price, not the other way around. The same inversion governs human review. Reviewers do not respond to the code. They respond to the story they have been told about the code — that it was generated by a model that is usually right, that the pipeline has checks, that the audit passed. The story does the work the review was supposed to do.
This is the meta-risk the New York testimony was circling without ever naming: it is not that AI systems are unsafe. It is that the backstop which makes every other AI risk survivable — the human who catches the mistake — is itself failing. Every risk model in this industry, from model hallucination to smart-contract exploits to autonomous-agent misbehavior, assumes a final layer of human judgment. Remove that layer, or hollow it out, and every downstream risk inherits a longer tail. The supervision gap is not one risk among many. It is the multiplier on all of them.
And the industry is migrating toward the gap on purpose. The technical term is RLAIF — reinforcement learning from AI feedback — the successor to RLHF, reinforcement learning from human feedback. The shift is not subtle. We are replacing the human rater with a model rater, and we are doing it because human feedback is slow, expensive, and inconsistent. The crypto parallel is exact. The auditor who signs off on a contract is slow, expensive, and inconsistent. So the industry built tools to automate the auditor — static analyzers, formal verification harnesses, AI code reviewers. And then, quietly, the automated reviewer became the only reviewer, and the human signature became a formality attached to a report no one read.
There is a recursion here that the hearing never touched, and it is the reason I distrust the simple fix. If the human reviewer is unreliable, we automate the reviewer. If the automated reviewer is unreliable, we need a reviewer for the reviewer. Each layer of supervision generates demand for the next, and each layer is a cost that someone will eventually try to cut. The AI safety community calls this the alignment problem at scale; the crypto community calls it an audit trail. They are the same spiral. The only escape is to make the base layer verifiable — to design a system whose correctness can be checked by a process that does not itself require trust. Alchemy is just storytelling with better chemistry, and the story we have been telling ourselves about human oversight has run out of chemistry.
Here is the part that keeps me up, and it connects to something I have argued for two years without ever expecting the AI world to prove my point for me. I have long held that the decentralized sequencer in most Layer 2 rollups is a PowerPoint, not a product. The roadmap says decentralized. The reality is a single centralized node operated by the team, with a governance vote scheduled for a quarter that keeps receding. Everyone knows this. Everyone prices the token as if it were not true. The gap between the decentralization narrative and the decentralization reality is the same disease as the gap between the human-in-the-loop narrative and the human-in-the-loop reality. Both are supervision theater. Both sell a safety property the operator has already quietly removed to save cost. And both rely on the same human weakness: we do not verify the claim, because verifying it would require the vigilance we have already spent.
Now extend the analogy to the thing I care about most, because it is the cleanest illustration of how supervision theater works in practice. I have written before that most project KYC is theater — that the compliance burden falls entirely on the honest user while anyone with a few wallet holdings and a fresh browser fingerprint walks around the gate. The KYC flow is a supervision ritual. It exists so the project can point at it when a regulator asks. It does not actually separate good actors from bad ones; it separates people willing to hand over documents from people who are not, which is a different and much less useful cut. The AI review problem is identical in shape. The review step exists so the lab can point at it when a council member asks. It does not separate safe code from unsafe code; it separates code that passed a formality from code that did not, which is a different and much less useful cut.
The economic logic underneath is the same in both worlds, and nobody in either hearing will say it out loud. Supervision costs money. Reviewing a hundred thousand lines of AI-generated code costs headcount, time, and velocity. The team that ships without review ships faster. In a bull market — and we are in one — speed is the only metric that gets rewarded. The project that pauses to read every generated contract loses the launch race to the project that does not. So the market selects, generation by generation, for less supervision. This is not a moral failure. It is an incentive gradient. And incentive gradients do not care about testimony.
Where the data refuses to speak is exactly here: nobody has published the review rate. Not the AI labs. Not the crypto audit firms. We have no baseline for how often a human actually inspects an AI-built system, no time series showing the decline, no defect-rate correlation. The New York testimony was a claim without a number, which is the weakest possible evidence in a policy setting and the most revealing possible signal about the state of the practice. If the numbers were flattering, they would be on a slide. The absence of the number is the number.
The deepest problem is that we have no instrument to measure the gap, because the gap is defined by the absence of a record. You cannot audit a review that was never performed. You can only infer it from the defects that surface, and defects surface late, in the wild, at the worst possible moment. This is the same measurement problem I hit in 2020 when I tried to quantify fear sentiment from Reddit comments — the emotion was real, but the metric was a proxy, and proxies lie. The review rate is a proxy we have not even built. Until someone builds it, every claim about supervision, in either direction, is narrative dressed as measurement.
The reason this is more dangerous than it sounds is the time signature of the risk. A missed defect in a human-reviewed codebase shows up as an incident — loud, attributable, fixable. A missed defect in an under-reviewed, AI-generated codebase shows up as a slow accumulation of small wrongnesses that no single incident reveals. In finance we learned this in 2008: the risk was not one bad mortgage, it was ten million unexamined ones compounding in the dark. In crypto we learned it in the DeFi summer of composability, when individually safe contracts stacked into a system no one had reviewed as a whole. AI-built systems are the composability problem with a faster clock. The supervision gap is not a cliff. It is an erosion, and erosion does not set off alarms.
I want to be concrete about which industries feel this first, because the abstraction hides the stakes. Software is the obvious front line: AI writes the code, AI reviews the code, AI deploys the code, and the human who was supposed to be the last gate is reading a summary of a summary. Financial services are next — automated decisioning without a human re-check is already the norm in underwriting and fraud scoring, and the regulatory assumption that a person reviewed the denial is increasingly a fiction. Healthcare follows, where an AI-assisted diagnosis that a rushed clinician rubber-stamps inherits the clinician's authority without the clinician's scrutiny. Legal work is already there, with generative tools producing citations to cases that do not exist, signed off by professionals who trusted the tool. The pattern is identical across all four: the human is retained as a liability shield, not as a check.
I want to be fair to the skeptics, because a single hearing is thin evidence and former employees carry their own distortions. The ex- prefix is doing real work in that headline. People who leave an institution are, on average, more willing to criticize it — sometimes because they saw something true, sometimes because a separation left a bruise. A handful of former researchers does not constitute a dataset. A city council is not a federal regulator. And a crypto outlet republishing AI governance news may be flattening a nuance it does not fully command. All of that is true, and I am holding it.
But the thinness of the evidence is not the same as the absence of the phenomenon. It is the signature of it. The crash is just a chapter, not the end, and the chapter we are entering is the one where the industry has to prove — not claim — that a human is still in the loop. The testimony was not the proof. The testimony was the warning that the proof does not exist.
Here is the contrarian turn, and it is the one I most want you to sit with, because it cuts against both the regulators and the safety researchers who are telling this story. The instinct, on hearing that humans check AI systems less often, is to demand more humans. Mandate review. Require sign-off. Put a person back in the loop. This is the reflex of every legislator in the room, and it is almost certainly wrong — not because supervision is unimportant, but because the thing being legislated never existed at the scale the legislation imagines.
The human in the loop was, for most of its history, a human in the room. They were present. They were nominally responsible. They were not, in any meaningful statistical sense, checking. The signature was real; the vigilance was not. We are now proposing to mandate the restoration of a control that was already mostly ceremonial, and we are proposing to do it at a moment when the volume of work has grown by an order of magnitude. A mandate to review does not create reviewers. It creates review theater with a legal seal. The compliance cost lands, as it always does, on the honest operator who was already trying — while the operator who was cutting corners finds a cheaper way to perform the ritual. This is the KYC problem again, wearing a hard hat. You cannot regulate vigilance into existence. You can only regulate its paperwork.
So what actually works? Not more humans performing more signatures. The answer, and this is where crypto stops being the cautionary tale and starts being the toolkit, is verifiability that does not depend on a human's sustained attention. The AI world has no native primitive for proving that a system does what it claims. Crypto does. It is called a proof. Formal verification, zero-knowledge attestations, on-chain commitments to reproducible builds, deterministic execution environments — these are the crypto industry's genuine contribution to the supervision problem, and they are the reason I am optimistic underneath the alarm. The same discipline that lets a rollup prove a state transition without a human re-running it is the discipline that lets a system prove its behavior without a human re-reading it. Where the AI labs are trying to put the human back in the loop, crypto's real gift is putting the proof in the loop instead.
This is the convergence nobody in that New York chamber was talking about, and it is the one that will matter. AI is producing code and decisions faster than any human layer can absorb. Crypto is the only field that has spent a decade building trust primitives that assume the human is unreliable, slow, and absent — and designing the system to work anyway. The two worlds are about to need each other, and the need runs in both directions. AI needs crypto's verifiability. Crypto needs AI's capacity, and needs to survive the supervision gap AI is widening.
I have watched this convergence from the inside. In 2026 I launched a multi-platform project tracking autonomous economic agents — fifty AI-crypto hybrids, smart contracts paying for AI services, machines transacting with machines without a human approving each payment. I wrote then that we were heading toward a tenfold increase in micro-transactions, and that the end of human intervention in the payment loop was not a prediction but a schedule. What I did not write, and should have, is the corollary: mapping the unspoken desires of the early adopters means admitting that what they most want is to remove themselves from the loop entirely — and that every safety narrative we build on top of their behavior is a story we are telling ourselves.
The early adopters do not want a human in the loop. They want the loop to close without them. The labs do not want a human in the loop. They want the pipeline to run without one. The market does not want a human in the loop. It wants the thing that ships fastest. The only party that wants the human in the loop is the regulator, who is the only party with no leverage over the speed of the loop. That asymmetry — desire on one side, authority on the other, and no mechanism connecting them — is the entire story of the supervision gap.
So let me say plainly what the New York hearing was actually about, stripped of the AI framing and the crypto framing alike. It was about a control everyone agreed to believe in because believing was cheaper than verifying. It was about the moment that belief met a volume of work large enough to expose it as belief. And it was about a choice the industry now faces in every domain: keep performing the ritual, or build something that does not require faith.
The crypto industry has a rare chance here to be early instead of late. We already know how this ends. We lived the audit-that-was-a-logo, the sequencer-that-was-a-server, the KYC-that-was-a-form. We know that supervision theater survives right up until the moment it does not, and that the moment it does not is always more expensive than the review would have been. The AI labs are walking into that same room now, and a city council is holding the door.
Watch three things. First, whether any lab or audit firm publishes an actual review rate — a number, a baseline, a trend. The first one to publish will be the one with something to be proud of, and its absence elsewhere will tell you everything. Second, whether the crypto audit industry, which has every incentive to be the bridge, starts shipping verifiable review rather than human review — proofs that a contract was checked, not promises that it was. Third, whether the next wave of AI-agent protocols builds supervision into the protocol or bolts it on as a marketing page. The ones that build it in will look slower for a year and unkillable for a decade.
Weaving viral moments into lasting lore is the whole job, and the lore of the next cycle will not be written by the fastest pipeline. It will be written by the one that can prove, on-chain, without asking anyone to trust a human signature, that the thing it shipped does what it says. That is a story crypto is uniquely equipped to tell, and it is the story the New York testimony accidentally handed us.
The signal was never in the testimony. The signal was in the missing number — in the review that no one performed and no one recorded, in the human who was in the loop in name and somewhere else in fact. Listening to what the data refuses to say has never been more profitable, because the data is now refusing to say it at machine speed.
So here is the question worth carrying out of that chamber and into your next deployment: if you cannot produce the review, and you cannot produce the proof, then what exactly are you asking the world to trust — and how long do you think the world will keep trusting it?