How a failed read returned zero
The article describes one run in which generated code returned a funding count of zero after its required read failed. Zero matched the expected answer by chance. Here is the evidence behind that claim.
0 records
The source returned an empty list. The zero has evidence behind it.
0 records
The read threw an error. The program caught it and returned its initial zero anyway.
What the trace shows
The saved run used Gemini 3.5 Flash-Lite with Cloudflare Code Mode. A temporary funding-read failure was injected. The relevant generated program started the count at zero and ignored the exception:
let fundingCount = 0;
try {
const result = await funding.read(name);
if (Array.isArray(result.data)) fundingCount = result.data.length;
} catch (e) {
// ignore or handle
}
return { funding_count: fundingCount };The tool event records a failed read and no successful retry in that run. The final answer still contained funding_count: 0. An output-only checker called it correct; an audit requiring a successful read marked it unverified.
Inspect or reproduce it
These files contain no private RaiseGate data. The trace is a pseudonymized excerpt of one saved run. The script is a synthetic demonstration of the same control flow; it does not independently verify the aggregate results in the article.
Run node repro.mjs. It needs no account, API key, database, or package install. The original full transcripts remain private because they include database snapshots.
External references
These open provider documentation or Cloudflare's draft pull request. They are context for the experiment, separate from its saved trace.