Memory is usually sold as a storage problem. Give the agent a vector database. Add a recall layer. Save summaries. Search harder. Expand the context window until the budget department starts making eye contact. Then ask the agent a simple question: what changed after the earlier conversation? That is where the polite demo often turns into a fog machine. ...
Search looks cheap until you try to train it. A business can usually collect plenty of questions. Employees ask support bots why a policy changed. Analysts ask internal search systems for comparable transactions. Legal teams ask where a contract clause first appears. Researchers ask agents to chase a multi-step trail across documents, web pages, and databases. ...
A car does not care whether an AI answer is impressive. It cares whether the answer arrives before the intersection. That small timing problem is where a large part of today’s agentic AI discussion becomes unserious. We keep asking whether models are smart enough to act. In cyber-physical systems, the more painful question is whether the system around the model can make action repeatable, bounded, and recoverable when the model is late, vague, or simply wrong. ...
Scoreboards are comforting. They reduce a messy contest into one neat line: winner, loser, maybe a score. Executives like them, product teams like them, investors like them, and benchmark dashboards absolutely adore them. Strategy, unfortunately, is rude enough not to fit inside that line. A company can make the right decisions and still lose because the market turns. A trading agent can survive a bad regime by managing exposure well, then look mediocre because the final return is not spectacular. A planning system can stumble into success after making terrible intermediate choices. Outcome-only evaluation is clean, but cleanliness is not the same as truth. It is often just a good-looking loss of information. ...
Tool calls look clean in a demo. A user asks for something. The model thinks. A browser opens. A database is queried. A spreadsheet is updated. A draft email appears. Everyone smiles, because apparently we now have an “AI agent.” Then the production version fails for a reason that is somehow both tiny and catastrophic: a tool schema was renamed, a memory field was serialized differently, a retry policy changed, a prompt template compressed one instruction too aggressively, or a guardrail blocked the wrong intermediate step. The model did not become stupid overnight. The architecture quietly moved the steering wheel. ...
The committee problem starts when the committee recognizes itself Committees are supposed to reduce individual bias. Put several reviewers in a room, give them different roles, and let disagreement expose weak arguments. This is the polite theory of institutional decision-making. It is also the theory behind many multi-agent AI pipelines. A critical model reviews the claim. A balanced model moderates the tone. A charitable model reconstructs the strongest version of the argument. A supervisor aggregates the outputs. Somewhere nearby, a fact-checking layer pulls external evidence. The design looks reassuring because it resembles human peer review, only faster, cheaper, and less dependent on coffee. ...
Failure should be boring Approval workflows are supposed to be boring. A client submits documents, a system checks the required conditions, and an approval either happens or does not happen. Boring is good. Boring means the process does not accidentally approve a case while also escalating it as problematic. The trouble begins when a workflow is written as a best-effort model of reality. Someone encodes the actions. Someone else adds an exception. A third person adds a shortcut because the quarterly dashboard prefers speed over philosophy. Eventually, a sequence exists that should not exist. It does not look like a bug when inspected locally. Each action seems defensible. The path as a whole is the problem. ...
A name can do a suspicious amount of work. Give an LLM a table of colorectal cancer gene candidates and ask it to rank the best drug targets. When the gene names are visible, KRAS lands at #1. The model justifies the choice with a confident reference to “proven therapeutic tractability via covalent RAS inhibitors.” Sensible enough, if the task is to combine the supplied table with the model’s accumulated biomedical knowledge. ...
Supermarkets look simple from the aisle. Milk is cold. Apples are stacked. Shampoo is there because, apparently, civilization requires thirty-seven variants of “moisture repair.” Behind that calm retail surface is a coordination machine that never really sleeps: demand planners, inventory teams, procurement staff, suppliers, warehouse coordinators, truck schedules, exception reports, and the occasional emergency because one popular SKU suddenly became everyone’s personality for the week. ...
Tools do not make an agent; they make the failure more interesting Camera. Browser. Crop tool. Search engine. Python sandbox. That sounds like the beginning of an intelligent workflow. Give a multimodal model these tools, and it should move from merely seeing the world to actually doing something with it: zoom into the blurry sign, search the extracted clue, cross-check the result, and produce the answer. ...