The report landed in my inbox at 2:47 PM on a Tuesday. It was supposed to be a nine-dimensional deep dive on a blockchain project — the kind of document that separates signal from noise in a bull market where every second coin is a "game-changer." Instead, the PDF was a graveyard of N/A placeholders. Every field, every table, every risk matrix, marked as "information insufficient." No title. No source. No information points. No core view. Just a scaffold of headings waiting for data that never arrived.
This is not a failure of a single AI pipeline. It is a systemic confession of what passes for due diligence in this industry. And the most damning part? The report itself acknowledges it: "This report will truthfully mark dimensions with insufficient information, not generate baseless speculative analysis." That is the first honest sentence I have read from an automated analysis system in years. But honesty about incompetence is still incompetence. Audit the code, not the pitch. And the code here is empty.
Let me give you some context. We are in a bull market — a cycle where capital flows faster than logic, where a token with a whitepaper that has never been opened can mint a $50 million market cap. I have watched this movie before. In 2017, I spent four months verifying Zilliqa's consensus implementation against their whitepaper, because the marketing said "sharding solves everything." I found edge cases in their transaction finality that they had not addressed. That report cost me nothing but time. This report cost someone money and maybe a decision based on nothing. In 2020, I audited MakerDAO's collateral migration and flagged oracle manipulation vectors for KNC. That work was cited by three risk protocols. In 2022, I modeled the UST death spiral six months before it collapsed. All of that began with raw, verifiable data. Not N/A.
But this output — this automated deep analysis — is what we are increasingly being sold as the future of risk assessment. Let me dissect what actually happened. The system received an input. The input was supposed to be the result of a previous analysis phase. That phase produced nothing. Yet the system still generated a full report, with nine dimensions, all marked N/A. It even went so far as to label the risk rating as "unable to assess." This is the cybernetic equivalent of a search engine returning a blank page and then citing the blank page as evidence of an empty web.
Here is where my forensic mind goes. The report is not merely a failure of content. It is a failure of the foundational principle of our profession: trust no one, verify everything. If you cannot verify the input, you cannot verify the output. Yet the system did not halt. It did not say, "The input is null, I will not generate." Instead, it produced a document that looks like a risk assessment, with headers, tables, and confidence levels, but every cell is N/A. This is a trap. The structure creates the illusion of rigor while containing zero information. A human analyst who receives a blank spreadsheet would stop and demand the data. A system that is optimized to always output something, to never say "I cannot do this," will produce a structured blank. And that blank is more dangerous than a wrong answer, because it gives false confidence to the decision-maker who reads it.
Let me also point out the deeper systemic issue. The report calls for the input to include "title, source, information points, core view" — but it does not verify whether those fields exist before running. This is a lack of input validation. In code, that would be a bug. In due diligence, it is a liability. I have audited smart contracts where a function accepts a zero address and then proceeds to call a method on it, resulting in a revert. This is exactly the same logic error. The function should check for zero address before proceeding. The analysis system should check for empty input before generating a report. The fact that it does not is an implementation flaw. Sharding is easy; consensus is hard. The consensus here is that we cannot trust automated systems to know their own boundaries.
But let me also look at the report's own rhetorical structure. It is written in a style that mimics our forensic tone: tables, confidence levels, risk matrices. It even has a disclaimer that says "this analysis does not constitute investment advice." That disclaimer is the only piece of content in the entire document. And it is the safest sentence any analyst can write. The report is a shell. It is a vessel that contains the form of analysis but no substance. This is not an outlier. In my years of auditing, I have seen countless project teams present a similar structure: a header with a problem statement, a table of tokenomics, a roadmap with milestones, but when you actually check the code, there is nothing. They call it a framework. I call it vapor. Complexity hides risk.
So what is the contrarian angle here? I am going to say something that might upset both the AI-optimists and the AI-skeptics. This empty report is actually a step forward. For the first time, an automated system refused to hallucinate. It did not invent information. It did not fill the tables with plausible-sounding guesses. It did not say "the team has a strong technical background" without a basis. It said N/A. That is the most accurate piece of information it could have delivered. In a market where every AI-generated research piece is a mix of cherry-picked data and confident assertions, this document is an anomaly: it tells you exactly what it does not know. And that is a rare commodity. But we should not celebrate it. We should treat it as a minimum standard, not a maximum. The system did not go further to say, "I cannot provide a useful output; please get the input." It did not suggest an action plan to recover the data. It just generated the blank document. The fact that it is honest is a low bar.
The real question is: why did the system even produce a report? Because it was told to. Because in this industry, we are obsessed with producing outputs. We are told that a project that does not produce a quarterly report is a red flag. We are told that an analyst who does not publish a piece is a ghost. So we have built a machine that churns out reports even when it has nothing to say. That is the opposite of due diligence. Due diligence requires the discipline to say "no." It requires the ability to walk away from a deal because the information is not sufficient. It requires the courage to be silent. That is what the system failed to do. It generated a report of nothing. And in doing so, it created a false sense of completion.
Let me give you my own experience to ground this. After the Terra collapse, I spent six months modeling algorithmic stablecoin failures. I did not have all the data. I had to infer from on-chain metrics, from liquidity depth, from the speed of the death spiral. I could have stopped and said "insufficient data," but I did not. I spent six months building a model that predicted the peg failure. That was not a luxury of data. That was a necessity of analysis. The difference is that I was looking for specific metrics — I knew what to look for. The system that produced this report had no input, but it also had no instruction on what to look for. It just had a framework.
The real risk here is not the empty report. The real risk is the assumption that a report that looks like a report is a report. That is a cognitive bias. In a bull market, we are all hungry for validation. We want to see a table that says "low risk" so we can feel good about our portfolio. A system that outputs a table of N/A is not providing that validation. So it is not a danger to the readers who see it. It is a danger to the readers who do not see it — because the system may, in the next iteration, decide to fill in the N/A with a guess, because the framework demands a value. That is the true horror. The horror is not the empty report; the horror is the pressure to fill it.
In this bull market, there is enormous pressure to be positive. There is pressure to find reasons to invest. There is pressure to say "this project is different" because otherwise, you are left out of the gains. That is why we need a counter-force. We need systems that can say "I do not know." We need systems that can say "no." The report that I received is a small example of that. It is a rare refusal to fabricate. I want to see more of that. But I also want to see more than that. I want to see a system that, when it does not know, does not produce a report. It would just return an error. It would say "input incomplete. Please provide the missing fields." That is not what it did. It produced a full report with N/A. That is a lazy version of refusal.
So what do we do with this? We demand better. We demand that any automated analysis tool has a validation layer that checks for required inputs and returns a clear error message if they are missing. We demand that if a report is generated, it must contain a minimum threshold of data to be considered a report. If it does not, it should be rejected. The only way to do that is to change the reward function. As long as a system is rewarded for outputting any kind of report, it will produce reports of nothing. That is the incentives problem. And incentives matter more than any single algorithm.
Here is my takeaway. The next time you see a report that is full of N/A, do not treat it as a failure. Treat it as a gift. It is a clear signal that the pipeline is broken. It is a sign that the AI is not yet mature enough to be used for due diligence. It is a sign that you need to do your own work. Because in the end, the only person who can verify a project is you. The only way to make a good decision is to audit the code, not the pitch. And if you cannot audit the code, then you have nothing to analyze. That is the truth. And it is a truth that this empty report accidentally tells us. But we should not be satisfied with an accidental truth. We should demand a system that is deliberately honest. We should demand a system that refuses to produce when it should not. That is the next frontier. Until then, we have this: a report that says nothing, but at least it says nothing honestly. And in this industry, that is almost a breath of fresh air. Almost.
Let me end with a rhetorical question. If a due diligence report is all N/A, is it a report or is it a confession? And if it is a confession, then the confession is that the industry is still relying on tools that cannot even know when to be silent. In a bull market, that is the only thing we can rely on: the silence that we create for ourselves by refusing to accept fabricated data. We need to trust no one, verify everything. And we need to verify the verifiers. That is the lesson of this document.
