Most agent systems that claim to learn from experience are really just logging. They record what happened, feed some of it back into the next prompt, and call it memory. When that produces a better result once, the approach gets treated as proven. When it produces a worse result once, it gets thrown out. Either way a single run is deciding future behavior, and a single run is noise.
The interesting design question is not whether an agent can learn from experience. It is how much evidence should be required before that experience is allowed to change what the agent does.
Pending Patterns and Confirmed Patterns
The approach we settled on separates a pattern from a rule.
When the system reviews past work, it looks for clusters of similar situations with similar outcomes. If the same approach keeps succeeding, or keeps failing, that gets recorded as a tentative pattern with pending status. Pending means noticed, not trusted.
A pending pattern needs five separate confirming observations from later work before it is promoted to confirmed and treated as guidance the agents actually follow. If contradicting evidence shows up three times, the pattern deactivates automatically.
Those two numbers are the whole safeguard. Five confirmations means a pattern has to hold across independent situations, not just the one where it happened to work. Three contradictions means a rule that stopped being true stops being enforced without anyone having to file a bug.
Ten Kinds of Memory, Not One Log
Retrieval quality depends on knowing what kind of thing you are looking for, so the memory bank is typed rather than being one undifferentiated pile of history.
Skills store reusable approaches to categories of problems. Tools catalog every script and procedure the system can run. Projects track ongoing work so the system does not rebuild something it already has. Memories record short term events with their outcomes. Experience holds knowledge that stays true indefinitely. Rewards hold the behavioral rules, both the ones humans set and the ones learned from observation. Questions track what has been asked, with answers where they are known. Ideas park untested proposals. Cross references point at where information lives. People store what the system knows about the humans it works with.
Every query is ranked by semantic relevance using local vector embeddings, not keyword matching. Searching for how to deploy code surfaces entries about pushing to production, build processes and release management even when none of those entries contain the word deploy. The system returns a minimum of three results so an agent always has something to work with, and up to twenty when many entries are genuinely relevant.
Learning That Runs Without You
Three pipelines run continuously rather than waiting to be asked.
The self learning pipeline reviews recent work in three phases. It brainstorms improvements without restriction, then switches to a critical mindset and scores each idea honestly, discarding the ones not worth pursuing, then implements what survives as actual changes to how the system behaves.
The adaptive coding pipeline handles building and modifying software. It identifies what needs to exist, plans it, writes it, reviews its own output for bugs and quality problems, fixes what it finds, and verifies the result before calling the task complete.
The adaptive research pipeline goes and learns whatever the system does not know yet. It explores a subject broadly, searches for specifics, cross checks findings for accuracy, and files what survives into searchable knowledge every other agent can reach.
A brain agent sits above all three, reviewing logs, checking work for consistency, extracting behavioral patterns, and deciding what to prioritize next based on your goals.
The Threshold Is the Product
It is easy to build an agent that remembers things. It is harder to build one whose memory is worth trusting, and the difference is almost entirely about what standard of evidence you hold it to.
An agent that learns from every outcome will confidently tell you nonsense within a week. An agent that never updates is just an expensive script. The useful range is in between, and where you set the confirmation threshold is the real design decision.
The full breakdown of the pipelines, the memory types and the rewards engine is at https://www.aiappsapi.com/autonomousagents/
Top comments (0)