Agent Architecture

Logs are where agentic AI gets honest A business agent rarely fails in the dramatic way demo videos imply. It does not usually announce, with theatrical humility, that it has misunderstood the workflow, misread the screen, or built a wrong model of the task. More often, it produces a tidy chain of steps, a reasonable explanation, a few reassuring intermediate notes, and then quietly stores the wrong conclusion as if it were company policy. ...

When Less Proves More: The Case for Minimalist AI Theorem Provers Proof is a good place to test AI humility. In ordinary business writing, a model can sound confident, cite familiar patterns, and still be quietly wrong. The error may not surface until the contract is signed, the policy memo is circulated, or the spreadsheet has already acquired the authority of a sacred object. In formal theorem proving, the arrangement is less polite. The model writes code. Lean compiles it. The compiler either accepts the proof or sends it back covered in red ink. ...

Architecture is usually where AI enthusiasm goes to become expensive. A team starts with a capable model. Then it adds a planner. Then memory. Then a tool router. Then a critic. Then a second critic because the first critic was apparently too polite. A few weeks later, the “agent” works on the demo path, fails on the second edge case, and nobody can explain whether the problem is the prompt, the retrieval layer, the tool schema, the memory policy, or the small parliament of LLM calls now debating inside the workflow. ...

A report is not finished because the model “understands” the assignment. It is finished because the system still knows, two hundred actions later, which documents were read, which notes were trustworthy, which sections remain unfinished, and which half-baked intermediate answer should not accidentally become the final one. That is the boring part of agentic AI. Naturally, it is also the part most systems quietly fail at. ...

Repetition is where most automation systems quietly embarrass themselves. Ask an AI agent to book a hotel once, and it may inspect the screen, reason through options, click through menus, and eventually finish the task. Ask it to do something similar tomorrow, and many systems perform the same little theatre again: perceive, reason, click, wait, reason, click, apologize, recover. Very intelligent. Very expensive. Slightly absurd. ...

Workflow is where agent demos go to die. A user asks for something that sounds simple: “Assess flood damage in this coastal district after the typhoon.” The agent smiles, metaphorically, and begins its little ritual. It searches, summarizes, calls a tool, thinks again, calls another tool, corrects itself, forgets one preprocessing step, invents a plausible shortcut, then produces a confident final answer that looks fine until someone who actually understands geospatial analysis asks an inconvenient question: where did the corrected satellite imagery come from? ...

Delay is not a footnote in automation. It is the product. A customer support agent that takes thirty seconds to decide whether to escalate has already shaped the customer’s mood. A warehouse robot that produces the correct plan after the pallet has moved has produced something closer to poetry than control. A trading assistant that generates a gorgeous hedge after the market has repriced is not sophisticated. It is late, which is the expensive version of wrong. ...

TL;DR for operators An enterprise agent does not fail only because it forgets. Often, it fails because it remembers like a hoarder with a search bar. The H-MEM paper proposes a hierarchical memory system for LLM agents: Domain, Category, Memory Trace, and Episode layers, connected by positional child indices so retrieval can move from broad meaning to specific memory instead of scanning a flat pile of stored vectors.1 That sounds like software housekeeping. It is actually the main point. ...

TL;DR for operators Memory is usually sold as a comfort feature for AI agents: the assistant remembers your preferences, your workflow, your charming habit of naming files final_final_v7. Fine. But operationally, memory matters less as storage and more as control. The hard question is not whether an agent can remember. It is whether the agent knows when a remembered episode should override fresh exploration. ...

TL;DR for operators Most enterprise AI failures do not come from the model being “too small”. They come from the system around the model being too vague. A model gives an answer. The workflow accepts it. Nobody knows whether the reasoning path was valid, whether the data path was stale, whether the tool should have been called, or whether the whole process should be redesigned after repeated mistakes. Then someone asks why the AI confidently did something expensive. Excellent. We have automated the intern, but forgot to hire the supervisor. ...