RAG

Memory, Multiplied: Why LLM Agents Need More Than Bigger Brains Memory is where many AI demos go to die. The demo looks fluent. The agent remembers the last three messages, calls a tool, summarizes a PDF, maybe even smiles politely while destroying your calendar. Then you return tomorrow and ask it to continue a project involving a client, two documents, three images, and a corrected assumption from last week. Suddenly the “agent” becomes a very expensive intern with amnesia. ...

A research agent enters a company budget meeting. That sounds like the beginning of a bad consulting joke, but it is exactly where “deep research” systems are heading. The first generation of excitement was about capability: can an AI agent search, plan, decompose, synthesize, and write a report that feels less like a chatbot answer and more like an analyst memo? Fine. The next question is less glamorous and far more operational: can the company control how much research the agent performs before the invoice becomes a small weather event? ...

Training an AI model is often sold like a kitchen renovation: add more data, add reinforcement learning, install the shiny reasoning countertop, and suddenly the whole thing looks expensive enough to be intelligent. This paper is useful because it ruins that brochure. The authors of Atomic Skills are the Prerequisite: When Reinforcement Learning Synthesizes Compositional Reasoning, and When It Only Amplifies ask a deceptively simple question: does reinforcement learning create new reasoning ability, or does it only increase the probability of behaviors the model could already produce?1 Their answer is not the clean slogan either camp wants. RL can synthesize new compositional reasoning, but only when the model has already learned the right underlying atomic skills. Without that foundation, RL mostly polishes whatever behavior already exists. Sometimes that is reasoning. Sometimes it is just a better-trained shortcut wearing a lab coat. ...

A customer-support agent that remembers the wrong thing is often worse than one that remembers nothing. Nothing can be checked. Wrong memory arrives wearing the little hat of confidence. This is the uncomfortable problem behind long-term AI agents. Businesses want systems that remember customer preferences, project history, unresolved tickets, contractual context, previous exceptions, and the fact that the user did not, in fact, ask to restart the whole workflow from scratch. The usual engineering answer is to bolt on memory: save notes, retrieve similar snippets, stuff them into context, and hope the model behaves like a diligent assistant rather than a distracted intern with a filing cabinet. ...

Hospitals do not suffer from a shortage of medical text. They suffer from a shortage of medical text that machines can use without becoming dangerously imaginative. Clinical guidelines are full of thresholds, exceptions, disease associations, diagnostic pathways, and terminology that looks tidy only until someone tries to automate it. A guideline may say one thing about a biomarker in the context of cardiovascular risk, another in renal disease, and something subtly different when age, sex, postoperative status, or treatment history enters the room. This is exactly the sort of nuance that makes large language models useful—and also exactly the sort of nuance that makes them risky. ...

A user asks to be forgotten. The recommender team opens the dashboard, sighs quietly, and faces the usual menu of unpleasant options. Retrain the model from scratch, which is clean in theory and expensive in practice. Partition the data so only part of the system needs rebuilding, which sounds elegant until collaborative signals leak across groups like gossip at a small wedding. Or approximate the user’s influence with gradients and influence functions, which is efficient until similar users get nudged around because the model learned their tastes together. ...

A job portal is not supposed to feel like a maze. Yet that is exactly what many public employment systems become: a stack of modules, PDFs, notices, eligibility rules, language barriers, and search boxes that assume the user already knows what to ask. Convenient, provided the user has already done half the civil servant’s work. ...

Ask an enterprise chatbot the wrong question on the wrong day and the problem is rarely that the language model has forgotten how to write English. The problem is that it has been handed the wrong pile of evidence. That is the expensive little defect inside many retrieval-augmented generation systems. The model may be fluent. The corpus may be current. The vector database may be humming along like a well-funded filing cabinet. Yet the answer still disappoints because the system chose the wrong snippets, placed a useful document too low, missed a newly relevant runbook, or treated yesterday’s user intent as if it were carved into basalt. ...

Procurement is where compliance anxiety goes to acquire a purchase order. A laboratory wants to buy an item. Perhaps it is ordinary. Perhaps it is dual-use. Perhaps it belongs under the U.S. Munitions List, Nuclear Regulatory Commission controls, the Commerce Control List, or the broad residual category of EAR99. The practical question is not just “what is this?” It is “what is this under the rules, according to which rule text, with enough evidence that someone can defend the decision later?” ...

A citizen-facing AI assistant is where the PLLuM story becomes interesting. Not because a chatbot in a government app is a dazzling concept. It is not. Most public-sector chatbots have the charisma of a PDF with a search bar and the legal confidence of a nervous intern. The interesting part is what Poland had to build before such an assistant could be considered remotely serious: a rights-managed national corpus, Polish-native instruction data, preference alignment, safety filters, RAG evaluation, retrieval tooling, and a family of public models with different licence regimes. ...