Enterprise AI

Tutorials are where software knowledge goes to become useful, messy, and mildly unbearable. A human trying to learn GIMP, LibreOffice Calc, Thunderbird, or VS Code can survive this mess. We search YouTube, skim a video, ignore the creator’s life story, watch the cursor, and remember that the menu item we need is not where our intuition said it would be. A GUI agent, even a strong vision-language model, has a harder time. It may see the screen. It may understand the instruction. It may even know the general category of action. Then it clicks the wrong menu because the software has its own local customs. Software, regrettably, has culture. ...

Customer support bots are not supposed to have enemies. They sit politely inside enterprise websites, read policy documents, retrieve relevant snippets, and answer questions with the soft confidence of a well-trained assistant. The selling point is simple: Retrieval-Augmented Generation, or RAG, should make large language models less likely to hallucinate because the answer is grounded in external evidence. ...

Thinking is expensive. That sounds obvious when the thinker is a human consultant billing by the hour. It sounds less obvious when the thinker is a large reasoning model producing long chains of thought, checking itself, trying another route, doubting the first answer, then generously spending another few thousand tokens to arrive at the same wrong place with better punctuation. ...

Write-Back to the Future: When Your RAG Starts Learning A RAG system usually fails in a very ordinary way. The retriever finds something relevant, but not quite enough. The generator receives five passages, three of which are useful, one of which is decorative furniture, and one of which looks relevant only because it shares the right vocabulary. The answer is then expected to emerge from this little committee of half-helpful paragraphs. Sometimes it does. Sometimes it does what committees do. ...

The agent keeps looking in the wrong place An incident happens. A service slows down. A pod restarts. A dashboard turns the tasteful shade of operational panic. The enterprise AI agent is asked to help. It reads logs, calls tools, inspects metrics, follows traces, and produces a plausible chain of reasoning. Sometimes it finds the root cause. Sometimes it wanders through the topology graph like a consultant discovering Kubernetes for the first time. ...

Retirement is not just an HR event. In many organizations, it is a data-loss event with a farewell cake. A veteran maintenance worker leaves. A senior nurse changes hospitals. A plant supervisor retires after thirty years of noticing small abnormalities before anyone else sees them. The company still has manuals, checklists, inspection records, training videos, and perhaps a cheerful knowledge portal that everyone praises and nobody searches. What disappears is harder to name: the half-formed judgment, the workplace memory, the sense that “this noise is different from last month’s noise.” ...

A memory mistake is still a mistake Memory sounds comforting until it remembers the wrong thing. Imagine a clinical AI agent facing a patient whose disease appears to be regressing after prior treatment. A past case in memory says that conflicting cancer signals should not be trusted too quickly. That sounds relevant. It even sounds cautious, which is the preferred costume of many bad decisions. But in this case, the regression is not noise. It is the signal. Treating it as a conflict leads the agent toward unnecessary systemic therapy rather than watchful waiting. ...

Documents change. That sounds too obvious to deserve a research paper. Product documentation changes. Compliance rules change. APIs are deprecated. Security policies are replaced. A customer support article says one thing in January, a release note quietly reverses it in March, and the enterprise search system confidently retrieves both as if time were just a decorative metadata field. ...

From One Shot to Many: Why AI Should Stop Guessing and Start Exploring One answer is tidy. One answer is easy to grade. One answer also happens to be a strangely fragile way to use AI. That is not just a philosophical complaint about creativity, brainstorming, or whether a chatbot sounds confident enough while being quietly wrong. It becomes a technical problem when AI systems generate artifacts that other systems must consume: code, formal specifications, compliance rules, database transformations, contracts, workflows, or mathematical statements. In those settings, the generated object is not merely a sentence. It is an interface. ...

Failure is usually where an LLM training pipeline becomes wasteful. A model generates a weak answer. A judge gives it a low score. The trainer nudges the policy away from that behavior and asks the model to try again. Repeat the ritual with more samples, more rollouts, more compute, and more optimism than the situation strictly deserves. ...