Postmortem: the warm voice that offered booked dates

world. The AI would keep offering dates to my clients that did not exist. A couple writes in excited about a Saturday in October. The model wants to be warm. Layer three is doing its job. So, it says something lovely about how beautiful the property is at the time of year and how it would love to hold the date for them. Except that that date is booked. The model didn't know that. It was never given the calendar. It was researched for an encouraging specific confident answer because it knew that what good service sounded like. And it was confident that these models produce something, but it didn't actually know the thing. And here is the thing. Every layer above did its job. The identity rules held. The mode was right. The voice was perfect. But, the voice was also the problem. A warm, confident voice offering something that isn't real is worse than a cold one because the couple now believes they have a date. You haven't given them good service, you've given them a disappointment with a 48-hour delay on it. This is where I understood that the whole talk is really what the whole talk is really about. The first three layers are all probabilistic. There are instructions to a system that usually follows instructions. Usually is completely fine when the cost of being wrong is a slightly off-brand sentence. It is not fine when the model is confidently inventing a fact that a real person is about to act on. A date, a price, a policy, a promise. So the veto is actually the cheapest layer to build and it's the only one that's deterministic. It reads what the model actually wrote, not just what you asked it to write. And it checks the specifics against what is real. A date the model offered that isn't in the allow list doesn't ship. Prevention is the prompt. If the veto is the check, you need both because the prompt will eventually lose and you don't want to find out that it lost by reading a couple's reply. It's