• Home
  • News
  • Blog
  • Releases
  • LLM history
  • Compare LLMs
  • Library
  • About
⌘K
Sign in

A blog and notes on development. The easiest way to reach me is via the social links below.

Contacts
talalaev.misha@gmail.com
Documents
Personal data processing policyPersonal data processing consent
Photo: Brecht Corbeel / Unsplash

An Architecture for LLM Agents That Captures Failures, Not Just Successes

Sh0ny
Sh0ny
29 июля 2026
  1. Home
  2. Blog
  3. An Architecture for LLM Agents That Captures Failures, Not Just Successes
1 min read

In short

An Analysis of the llm-wiki-memory-template: How an append-only wiki between sources and agents solves the problem of losing negative results and memory across sessions. Why this is more important than yet another benchmark.

LLM agents write code and conduct research, but their memory is reset after each session. RAG based on raw sources isn’t helpful: it doesn’t retain context. As a result, teams endlessly repeat the same mistakes because dead-end branches and discarded hypotheses aren’t preserved—neither in publications nor in repositories.

The llm-wiki-memory-template architecture offers a solution: an LLM-powered, linked wiki between raw sources and the agent. The key idea is “append-only” by default. The wiki stores not only what worked but also the failures. This solves the problem of lost negative results, which publications and code sharing structurally fail to address.

The template is designed as a substrate for collaboration in three dimensions: “human-human,” “human-AI,” “AI-AI.” Each layer is supported by a separate architectural element.

The authors tested the approach on three deployed use cases and one design. The most illustrative example is a project by two of the authors. A retrospective audit revised the reported accuracy of two previous experiments: from the reported 20 out of 20 to 14 and 12 based on evidence, and then to 18 and 18 after correction. The error path was preserved in the artifact.

The authors’ main thesis is that preserving failure paths, agent honesty, and appropriation are end-to-end socio-technical properties of the artifact. These are not merely technical mechanisms.

For practitioners, the conclusion is clear: if your agents do not remember what they have already tried and why it did not work, you end up paying for the same mistakes over and over. This pattern is worth studying for those building pipelines with long-term memory for agents.

Source: cs.AI updates on arXiv.org

новостиaillmагенты
More AI-tool write-ups on the Telegram channel — short and to the point
Subscribe on Telegram

Comments

(0)
​