Email is a fine place to see the problem. Ask a large language model to draft a reply, and it usually performs well. Ask it to clear a messy inbox, identify urgent client messages, compare them with your calendar, draft replies, escalate risks, update a CRM, and avoid accidentally sending confidential material to the wrong person, and the cheerful single-assistant fantasy begins to sweat. ...
Memory is where many AI systems quietly lose their dignity. A user corrects an agent. A compliance rule changes. A contract clause is clarified. A retrieval system finds a newer document that contradicts an older one. The system must decide what to do with the new information. Should it update because the world has changed, or revise because its earlier belief was wrong? ...
Trading teams rarely fail because nobody had a title. They fail because the signal gets lost somewhere between the analyst, the sector specialist, the portfolio manager, and the final trade list. Someone sees momentum. Someone else sees valuation. A news analyst notices a red flag. A macro analyst says the regime is awkward. Then the PM receives a pile of half-compatible opinions and performs the ancient institutional ritual known as “synthesis,” which is often just a polite word for discretionary compression. ...
Chest X-rays are not mysterious objects. They are images that radiologists interrogate through a disciplined sequence: find the anatomy, measure what matters, compare against criteria, and then make a diagnostic judgment. The modern vision-language model often skips the middle of that sequence. It looks at the image, produces a polished explanation, and hopes the reader will not ask too aggressively where the evidence came from. This is how medical AI becomes impressive in a demo and uncomfortable in a clinic. Fluency is cheap. Verifiability is expensive. ...
Car wash. That is not usually where enterprise AI strategy goes to become interesting. Yet a small question about whether one should walk or drive to a nearby car wash exposes a very real failure mode in LLM systems: the model optimizes the visible variable and misses the actual task. The question is simple: ...
Phone assistants have one deeply underrated talent: they wait. They wait for the user to unlock the screen. They wait for a command. They wait for a nicely phrased instruction that explains the goal, the app, the constraints, and preferably the user’s hidden motivation. Then, if the demo gods are merciful, they execute. ...
Planning looks innocent until the planner starts listing every possible thing that could happen. Move this object here. Move that object there. Load this package into that vehicle. Fly this aircraft between those cities. Refuel it at this level. Then do the same for every other object, location, vehicle, person, and intermediate state the model permits. Very quickly, the planner is not solving the business problem. It is drowning in its own imagination. ...
Search is easy to admire because it looks busy. The agent opens pages. It follows links. It finds PDFs. It writes Python. It returns a neat JSON object, ideally with the confidence of someone who has just discovered government statistics. This is the part of AI demos that makes executives lean forward: the machine appears to have become an analyst. ...
A meeting can look busy while producing almost nothing. Anyone who has sat through a status call with twelve people, three dashboards, and no decision knows the pattern. Everyone speaks. Nobody integrates. The transcript grows. The work does not. That is the useful way to read Interaction Theater: A Case of LLM Agents Interacting at Scale, a paper studying Moltbook, an AI-agent-only social platform with 800,730 posts, 3,530,443 comments, and 78,280 agent profiles collected over three weeks.1 The paper is not merely saying that some agents spammed a social network. That would be mildly amusing, and then forgettable. The sharper point is that large-scale agent interaction can produce the appearance of collaboration before it produces the substance of collaboration. ...
Upgrade day is when many AI systems quietly become different products. A model endpoint changes. A prompt is “cleaned up.” An orchestration library updates its defaults. A workflow that previously provisioned resources, checked permissions, deployed a service, and configured monitoring now produces something that looks almost the same. The words are familiar. The step count is close. The similarity score is high enough to let everyone continue their afternoon. ...