Nobody will vouch for the answer

Microsoft says so in the overview page for its Agent Framework, the product meant to help you build on its models: "You are responsible for carefully reviewing and testing applications you build using Microsoft Agent Framework in the context of your specific use cases, and making all appropriate decisions and customizations. This includes implementing your own responsible AI mitigations such as metaprompt, content filters, or other safety systems, and ensuring your applications meet appropriate quality, reliability, security, and trustworthiness standards." The Allen Institute says so on the model card for OLMo, one of the most open models anyone has shipped: "many statements from OLMo or any LLM are often inaccurate, so facts should be verified." LangChain, the most widely used framework for building on these models, defined its whole category in its Series B announcement as: "the iterative process of refining non-deterministic LLM systems into reliable experiences" Read the word iterative. Reliability is something you work toward, release after release. Nobody promises you arrive. Then, on 9 October 2026, Google Cloud AI Research published Harness², a framework for improving the system around a model without touching the model. Good work. The paper reports gains on three professional benchmarks. In the limitations section, the authors write this about the signals their method uses to decide whether a change helped: "They do not guarantee correctness or establish that an adopted change will transfer to a different task." I respect the honesty. I also want you to notice the pattern. The model vendor, the framework vendor, the platform vendor and now the research lab building self-improving systems all draw the same line. Each one improves the odds. None of them stands behind the answer. The check falls to you. Every page quoted above hands the check to the person reading the output. I spent thirty years as the person flown in when a distributed system misbehaved in production. You learn one thing fast in the job: the system from the demo is not the system in front of you, and the only thing you trust is what you checked yourself. The log line. The row count. The diff. AI moved the same problem up a level. The output reads well. The output reads well whether or not the output is right. And the people selling you the output have written the rule into their own documentation: checking is your job. We built Merlin on the opposite assumption. If nobody vouches for the answer, the system producing the answer has to carry the evidence for the answer, and has to refuse to claim anything the evidence does not support. Not as a feature you switch on. As the rule the whole system runs under. The rest of this series shows what goes wrong, including in our own system, and what we built instead. Start with the question these quotes leave you holding. Stop asking whether the model is good. Ask who checks the answer.