Agents that learn from their own history can preserve mistaken rules. Falsification-Gated Self-Evolution (FGSE) addresses that by requiring each candidate memory to state the intended behavior and a falsifiable test before being committed. The proposed workflow runs target tasks, counterexamples and regression checks, then monitors updates after storage.…
Inspect the ClaimsCase · DiggingBeagle record
Falsification-gated agent memory reduced harmful accepted updates in controlled trials
Agents that learn from their own history can preserve mistaken rules. Falsification-Gated Self-Evolution (FGSE) addresses that by requiring each candidate memory to state the intended behavior and a falsifiable test before being committed.
Controlled agent-memory update benchmarks with testable outcome verifiers; no production poison-resistance guarantee.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- not established
- Evidence
- Grade B
- Remediation
- not applicable
- AI role
- AGAINST AI
Basis and provenance
Reported ablations compare a memory-commit gate under trusted verifiers. Live attacker poisoning and long-run adverse effects are not established. An impact band is not assigned because the available Claims do not establish a comparable verified severity or quantified harm.
Assessed Nov 12, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-R239-012-CORE · Falsification-Gated Self-Evolution challenges memory hypotheses before persistence and reduces harmful updates
At a glance
Memory admission must be a separate authorization boundary, not an automatic consequence of a locally successful run.
Read the implicationsVerifier compromise, misleading local success and long-duration memory drift remain untested.
Limits and uncertaintyFull account
Agents that learn from their own history can preserve mistaken rules. Falsification-Gated Self-Evolution (FGSE) addresses that by requiring each candidate memory to state the intended behavior and a falsifiable test before being committed.
The proposed workflow runs target tasks, counterexamples and regression checks, then monitors updates after storage. In the benchmark ablations, harmful accepted updates were 3.6% with the full gate versus 10.6% without falsification probes; post-commit violations were 3.1% versus 9.4%. Results depend on trusted verifiers and a limited evaluation environment. An attacker able to compromise the verifier or contaminate the regression archive might still get an unsafe rule admitted.
Memory admission must be a separate authorization boundary, not an automatic consequence of a locally successful run.
The mechanism reduces self-reinforcing errors under trusted probes but creates a new verification dependency. An attacker who controls archived traces or the check used to label success may still insert a persistent wrong rule. This differs from WikiTrace, which preserves source trajectories for later inspection but does not itself prove that a trajectory is authentic.
Mechanism and trust boundary
- 01
A successful agent episode proposes a reusable memory rule.
- 02
The system specifies a prediction, verifier, counterexample probes and historical regression tests before admitting that rule.
- 03
Only accepted memory is persisted, followed by monitoring of later outcomes.
Claims & evidence
CLM-R239-012-COREFGSE reports 3.6% harmful accepted agent-memory updates with falsification probes, compared with 10.6% in the ablation without those probes.supported
Basis: reported finding
- supportsFalsification-Gated Self-Evolution challenges memory hypotheses before persistence and reduces harmful updatesprimary disclosure
Section 6.3 ablation, harmful-update and post-commit-violation columns
Implications
Memory admission must be a separate authorization boundary, not an automatic consequence of a locally successful run.
Controls and mitigations
- Demand independently reproducible memory admission tests, counterexamples and rollback; treat both summaries and original traces as untrusted until validated.
Unknowns and contradictions
- Verifier compromise, misleading local success and long-duration memory drift remain untested.
Sources and citation
Material revision history
- Nov 12, 2026 · Published version · first publication · revision 241