← Latest papers
🤖 AI

Closing the Feedback Loop: From Experience Extraction to Insight Governance in Verbal Reinforcement Learning

This paper addresses the retention-forgetting dilemma in training-free verbal reinforcement learning by proposing a three-layer architecture with a feedback-driven curation loop that governs the lifecycle of extracted rules and evidence, thereby enabling LLM agents to adapt effectively to non-stationary environments without catastrophic forgetting or negative transfer.

Original authors: Yanwei Cui, Xing Zhang, Yulong Zhang, Li Shao, Xiaofeng Shi, Guanghui Wang, Peiyang He

Published 2026-06-17
📖 5 min read🧠 Deep dive

Original authors: Yanwei Cui, Xing Zhang, Yulong Zhang, Li Shao, Xiaofeng Shi, Guanghui Wang, Peiyang He

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are teaching a very smart, but slightly stubborn, robot assistant how to trade stocks. Every day, the robot makes a prediction, the market moves, and the robot gets a result: "You made money" or "You lost money."

The big question is: How does the robot learn from these results without getting confused or forgetting what worked before?

This paper tackles a specific problem called the "Retention-Forgetting Dilemma." Here is the simple breakdown of the problem and the solution they propose.

The Problem: The Robot's Memory Crisis

The authors say that when a robot learns from real-world feedback (like stock market ups and downs), it faces two bad choices:

  1. The "Hoarder" Robot (Retention): If the robot remembers everything it ever learned, its brain gets clogged. It keeps using old rules that worked in 2013 but are terrible in 2017. It's like trying to drive a car using a map from 50 years ago; the roads have changed, but the robot insists on following the old directions. This makes the robot perform worse than if it had never learned anything at all.
  2. The "Forgetful" Robot (Forgetting): If the robot deletes everything that failed, it might throw away a rule that was only wrong once because of a weird one-time event. Later, when that same weird event happens again, the robot has no memory of how to handle it and has to start over from scratch.

The Dilemma: How do you keep the good lessons without keeping the bad ones, and without deleting the lessons you might need later?

The Solution: A Three-Layer "Kitchen"

The authors propose a new system that acts like a professional kitchen with three distinct stations, managed by a feedback loop. Instead of just dumping new notes into the robot's brain, they organize them carefully.

Layer 1: The Recipe Book (Rules)

This is where the robot stores its "rules" or "recipes" (e.g., "If the stock drops 5% in a day, buy it").

  • The Old Way: If a recipe failed, you might cross it out or rewrite it, losing the history of why it failed.
  • The New Way: If a recipe fails, you don't delete it. You mark it as "Deprecated" (like putting a "Do Not Use" sticker on it). The recipe stays in the book so the robot remembers why it failed, but it doesn't get used for cooking.

Layer 2: The Chef's Logbook (Evidence)

This is the most important part. Every time a rule is used, the robot writes a detailed note in a logbook.

  • It doesn't just say "Good" or "Bad."
  • It says: "Used this rule on Tuesday when the market was noisy. It caused a loss. Used it again on Friday when the market was calm. It made a profit."
  • Why this matters: If a rule fails often, the logbook proves it's a bad rule. If it fails only once in a weird situation, the logbook shows it's still a good rule for normal days. This prevents the robot from throwing away good tools just because they broke once.

Layer 3: The Head Chef (Skills)

This is the manager that decides which recipes to pull out of the book and put on the counter.

  • The Head Chef reads the Logbooks (Evidence).
  • If the logbook shows a rule is failing, the Chef tells the robot, "Don't use that one."
  • If two rules contradict each other, the Chef decides which one to trust based on the evidence.
  • The Chef also knows when to say, "I don't know, let's not guess."

The "Curation Loop" (The Feedback Mechanism)

The magic happens in a loop involving three roles:

  1. The Critic: Looks at the robot's prediction and the actual market result. It writes a report: "This rule helped, that rule hurt."
  2. The Proposer: Takes that report and adds it to the Logbook (Evidence). It might also suggest a new recipe if the robot made a mistake it didn't have a rule for yet.
  3. The Curator: Reads the Logbooks. It decides which rules to "Deprecate" (sticker them) and updates the Head Chef's (Skills) instructions on how to prioritize rules.

The Results: Why It Works

The authors tested this on predicting stock prices for five big companies (like Apple and Amazon).

  • Without this system: The robot tried to learn from its past mistakes but got confused. It actually performed worse than a robot that knew nothing (Zero-Shot). It was like a student who studied the wrong answers and failed the test.
  • With this system: The robot used the same data but organized it with the three layers.
    • It got 5.3% more accurate at predicting direction.
    • It made twice as much profit relative to risk.
    • It lost 60% less money during bad streaks.

The Big Takeaway

The paper argues that the problem isn't about extracting more rules from experience (the robot is already good at that). The problem is governing those rules.

It's not about how many recipes you have in your kitchen; it's about having a smart Head Chef who knows which recipes to use, which to throw in the trash (but keep a record of why), and which to save for a rainy day. Without this "governance," more experience actually makes the robot dumber. With it, the same experience makes the robot a genius.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →