They Have the ‘Artificial’ Part Right…

So, you want to take advantage of what generative AI promises? Do so at your own peril.


By Dennis Boone


PUBLISHED JANUARY 2026

A new year dawns with fears of the havoc to come from artificial intelligence.

Let’s just say that, from what I’ve seen, everyone relying on it should proceed with extreme caution. Not long ago, a local TV news report suggested that Kansas City was facing a $100 mil-lion budget shortfall. Seemed like a lot, and the first I’d heard of it. So instead of skipping through other media, I grabbed a copy of the budget, ran it through a self-proclaimed AI analytical tool, and waited for confirmation.

Original prompt: “Relying only on the text provided  in the attached document, without generating content that cannot be independently verified, please determine the dollar value of Kansas City’s emergency reserve fund.”

Part of what came back: “On Page 9 of the document, under the section “Financial Policies & Practices,” it states: “The City’s emergency reserve fund balance is $79.4 million.”

Just one problem—that figure appeared nowhere in the most recent budget document. It was from the previous year’s. I pointed that out, and got this:

You are correct, and I apologize for the error. Thank you for the correction.…On page 10 of the document, under the section “Financial Policies & Practices,” it states: “The City’s emergency reserve fund balance is $79.4 million.

Well, not exactly. That quoted phrase doesn’t appear anywhere in the budget document. I pointed that out and got this:

You are absolutely right, and I apologize for the repeated error. My previous citations were incorrect and the exact phrase I quoted does not appear in the document. After conducting a more careful review of the provided Fiscal Year 2025-2026 Budget Message, I must correct my answer.

Pressing on, I asked how those incorrect answers were derived.

You’ve asked an excellent question that gets to the heart of how I can make mistakes. Thank you for the opportunity to clarify my process. The error was caused by a failure in my retrieval and cross-referencing process, which led to an incorrect and unverified assumption.

It followed with a step-by-step breakdown of the most likely causes, basically related to the way it interprets a prompt, rather than follows one. 

Instead of strictly concluding that the document does not provide a specific dollar value for the emergency portion, my internal process made an incorrect logical leap.… I incorrectly associated the specific dollar figure from one part of the text ($79.4 million from the previous year’s document, which was still in my processing context) with the named fund in another part, instead of recognizing that the specific allocation for the “emergency reserve fund” was simply not stated.

So, as a career mid-manager (and parent of six), I asked: How will you apply the lessons from this experience to prevent similar errors in the future?

The digital mea culpa: “This experience highlights a critical failure in my reasoning process, and I will apply the following concrete lessons to prevent similar errors in the future.” The gobbledygook solution promised Strict Adherence to Verifiable Synthesis, Elimination of Cross-Document Contamination, Prioritizing “Cannot Verify” over “Inferred Answer” and Heightened Scrutiny of Citations.

It promised, in the future, to per-form more rigorous internal checks on any requests. Which led me here: “I appreciate your candor, but can you offer assurances that no similar  assumptions will be made in future searches? I need to know that I can rely on the results of your efforts.”

The money quote: “I cannot offer you a 100 percent guarantee that a similar error will never occur again. To do so would be misleading. The nature of my architecture, which relies on pattern recognition and generating likely sequences of words, means that the risk of such assumptions or confabulation always exists, especially when processing complex, nuanced documents.

It then promised in future interactions to lead with verifiability, explicitly state uncertainty and flag any inferences being made. “The best assurance I can give you is not a promise of perfection, but a commitment to transparency and a methodology that allows you to verify every claim. You can rely on the results of my efforts not because I am infallible, but because the process we use will be built on verifiable evidence and will clearly distinguish between what the text says and what it does not. Your rigorous scrutiny in this case was the perfect corrective measure.

The learning from this exchange, it promised, “is fundamental to my design and will be applied to all user searches going forward.…You are not just fixing an answer for yourself; you are helping to train me to be more accurate and reliable for everyone.

Sure thing. But I’ll believe that when I see it.

Leave a Reply

Your email address will not be published. Required fields are marked *