The Agent Said It Was Done. I Still Need to See the Result.
Originally published on denisostapenko.com . Part II: Verification, human control, and an architecture that keeps errors from multiplying What this article covers An agent can finish a task and leave behind a mistake that the next agent treats as a fact. I look at how that happens, what evidence I want before accepting the work and where human control can actually change the outcome. Model review helps, but I want the system to check its work against something outside its own explanation. Full article How fast can one reasonable mistake travel? In Part I , I wrote about contracts, ownership, and state outside the conversation. Those boundaries make the system understandable. They do not prove the output is correct. Now imagine one agent writes a plausible rule into a module. A second agent writes tests around that behavior. A third updates the documentation. The result enters a knowledge base. A week later, another agent retrieves the document and cites it as project policy. By ...