Why your LLM product hallucinates the one thing it shouldn't, and the architectural pattern that fixes it

A woman forwards a conversation with her boyfriend to my AI bot. The model detects danger signals (emotional abuse, isolation tactics) and responds with a crisis hotline number. Caring. Responsible. One problem: it's a children's hotline. The model hallucinated a crisis contact for an adult in distress. The prompt says "DO NOT invent contact information." Doesn't matter. The model's drive to be helpful is stronger than any instruction. This is not a prompting problem. This is an architecture problem. The single-pass trap The typical LLM product architecture: user input goes into the model, model output goes to the user. If you need the model to both analyze input and present the result in a specific voice, tone, or format, both jobs go into one prompt. This is where things break. Analysis demands precision and structure. Voice demands freedom and empathy. These are conflicting objectives competing for the same token budget. The result: the model weaves hallucinations into convincing pr