Your agents learn while doing the work. They discover where the organization’s guidance no longer matches reality. But when the conversation ends, most of that learning disappears with it. Agent memory may preserve some of it for you. What about the rest of the organization?
For agents to work effectively inside an organization, they need access to its knowledge. They need to know which APIs to use and which services already exist. They need current conventions and clear warnings about deprecated approaches. The quality of that knowledge shapes every decision they make. The challenge is that organizational knowledge constantly changes. Documentation describes what we knew when someone last updated it, while everyday work keeps producing new evidence. Agents are increasingly present at the exact moment we discover that the guidance no longer matches reality.
Work produces knowledge
Imagine an agent implementing a feature. It recommends API A, and the developer corrects it: We don’t use API A for new applications anymore. Use API B. The developer solved the immediate problem, but the interaction also revealed that the organization’s recorded knowledge may be incomplete, outdated, or difficult to retrieve. What happens to that learning? Today, it will often remain in the conversation. The developer’s agent might remember it and avoid the mistake next time. But another developer will still face the same old recommendation tomorrow, make the same correction, and pay for the same learning again.
Agents also make discoveries on their own. An agent might try API A, encounter a constraint, and investigate alternatives until API B works. It completes the task, but its path exposed information that could help the next person. Without a way to capture that signal, the organization benefits from the result once and loses the reasoning that made it possible.
A discovery is a signal
Should every correction become organizational guidance? Of course not. API B may work only in one scenario. The agent may have misunderstood API A, while the human correction may reflect a team preference rather than an organizational decision. Older documentation may simply have been easier to find than the current guidance.
Human corrections and agent discoveries are signals. They tell you that something deserves a closer look. Treating each signal as truth would fill the knowledge base with contradictions and make future decisions harder. Ignoring them on the other hand, wastes evidence produced during real work. This gives us a useful distinction: capture potential learnings generously, then verify them before they influence everyone else. The cost of proposing a correction should be low. The standard for accepting it as current organizational knowledge, however, should be high.
Change knowledge like code
We already have a model for changing shared systems. When someone modifies software, they propose a change and another person reviews it before it reaches production. Organizational knowledge can follow the same pattern. An agent could recognize that a task produced a potential learning and propose the smallest useful change: New customer-facing applications should use API B rather than API A. A reviewer can compare that proposal with current guidance and check it with the team that owns the decision. Once verified, the update becomes available to other people and their agents.
The code change and the knowledge change need separate lifecycles. A pull request may be rejected while revealing a valid constraint that belongs in the organization’s guidance. Code may also be merged without teaching the organization anything new. Keeping the artifacts separate lets each one follow the review process it needs.
Keep current knowledge coherent
Suppose current guidance says to use API A, while a task suggests API B. Adding another document that recommends B leaves future agents with two plausible answers. Which one should they follow? More information has made the decision worse.
A reviewer needs to resolve what the signal means. If B supersedes A, update the current guidance. If B applies to a specific scenario, qualify the recommendation. If the knowledge already says B, the organization may have a retrieval problem rather than a documentation problem. An unresolved conflict should remain visible as a conflict until the owner makes a decision.
The goal is a coherent representation of what the organization currently knows. Version control can preserve that API A was once recommended, without forcing that historical guidance to compete with today’s decision. Decision records can explain why a particular application still uses A. Current knowledge answers a different question: what should we do now?
Preserve the boundary of the conversation
Agent conversations are valuable learning environments because they can be private. People can ask questions they would hesitate to ask publicly. They can explore half-formed ideas, be wrong, and change their minds without turning every thought into an organizational record. Closing the learning loop shouldn’t publish the conversation. The agent can extract a small candidate change while leaving the exchange private. Reviewers may occasionally need more context to verify a proposal, which creates a real tension between learning and privacy. Still, an organization can capture the useful claim without treating the whole conversation as knowledge.
Access boundaries matter too. An agent acts on behalf of a person and should see only the organizational knowledge that person can access. In a large organization, two agents may legitimately work with different views because confidential projects and sensitive systems require it. Shared learning should improve knowledge within those boundaries, not collapse them.
Close the learning loop
We usually describe organizational knowledge as flowing in one direction. The organization teaches the agent, and the agent does the work. But agents now participate in the work through which that knowledge evolves. They encounter stale guidance, discover constraints, and receive corrections from people who understand the context. Every one of those moments is an opportunity for the organization to learn: capture the signal, verify what it means, and update the current guidance only when the evidence supports it. That’s how agents can improve organizational knowledge without turning every observation into truth or every conversation into a public record. Your organization already pays for these discoveries. The question is whether the next person will have to pay for them again.