Research · July 2026
Learning-Augmented Generation
RAG taught machines to look things up. LAG is our wager that the next enterprise won't just answer questions — it will remember the answers, and get better because it did.
文章以英文發佈。
The plateau
Something strange happens about a year into most enterprise AI deployments. The demos were excellent, adoption is respectable, the answers are good — and the system is exactly as smart as the day it shipped. A thousand conversations, ten thousand resolved exceptions, a full year of decisions with known outcomes have flowed through it, and none of it left a trace. The organization is doing more, faster. It isn't learning faster.
That plateau isn't a model problem. It's a memory problem.
Retrieval is not memory
Retrieval-augmented generation was the right first step: ground the model in your documents so it answers from your reality instead of its training set. But documents are what an organization managed to write down — a minority of what it knows. The majority is experience: which supplier slips in monsoon season, why the discount structure changed last year, what the previous three attempts at this integration taught you. Experience mostly lives in people, until it leaves with them.
Retrieval answers questions. Learning accumulates capability.
LAG extends the augmentation one level up: generation informed not only by what the organization has written, but by what the system itself has seen happen — outcomes, corrections, decisions and their consequences, captured as first-class data rather than exhaust.
The loop, closed
Capture. Every meaningful action the system takes — every draft accepted or rewritten, every escalation upheld or overturned, every prediction confirmed or embarrassed — is recorded with its context and its result. Not logs for the auditors: experience for the learner.
Consolidation. Raw experience is noisy, and most of it doesn't deserve to be remembered. A consolidation stage decides what becomes durable memory: which patterns recur, which corrections were one-off human whim and which were policy, what should be forgotten and when. Forgetting is a feature — memory without curation is just a bigger haystack.
Recall. When the next decision arrives, the system retrieves not just relevant documents but relevant experience: the last time this pattern appeared, what was tried, and how it went. The new joiner's first day comes pre-loaded with the veteran's scar tissue.
Return. What was recalled shapes what is generated; what is generated produces new outcomes; new outcomes become new experience. The loop closes — and it runs where the real work happens, in production, from day one. Not in a lab, not in a pilot that never graduates.
Memory you can read
An organization cannot take responsibility for judgment it can't inspect — and a system that learns is a system that changes. So the memory itself is a clear stream: every learned behavior traceable to the experiences that taught it, every consolidation auditable, every deletion executable on demand. When a regulator, a customer, or your own compliance team asks why it behaves this way now, there is an answer with dates on it. Learning without provenance is just drift.
What it feels like
Concretely: the pricing debate your leadership settled last quarter doesn't get re-litigated by a system that wasn't listening. The exception your team taught it to catch in January is caught in March without anyone teaching twice. The answer to 'have we tried this before?' stops depending on who happens to be in the room. Small things, compounding weekly — the difference between an organization that uses intelligence and one that keeps it.
What we don't know yet
This is a research program, so honesty about the open problems. What deserves remembering is a harder question than how to remember it. Memory can be polluted — by bad outcomes recorded uncritically, by feedback loops that quietly reinforce a mistake. And evaluation is genuinely difficult: proving a system is better because of memory means separating learning from luck. These are the threads our team is pulling — in production systems, with partners who let us instrument reality instead of benchmarks.
The wager, stated plainly: intelligence is becoming abundant, and abundance makes accumulation the only differentiator left. The enterprises that win the next decade won't be the ones with access to the best models — everyone will have that. They'll be the ones whose systems have been quietly keeping what they learn. It's compound interest for judgment. The earlier the loop starts, the harder it is to catch.
Read the response: After the descent, the only moat is memory →