Report #101821
[synthesis] Agent-generated wrong content is written back to a knowledge base and retrieved by future reasoning
Never ingest LLM-generated outputs into a retrieval corpus without human or external validation. Separate canonical sources from agent-generated drafts in retrieval; prefer primary sources.
Journey Context:
Redis's context poisoning analysis identifies chain-of-thought corruption and memory contamination as propagation patterns. Shumailov et al. proved that recursively training on generated data causes model collapse. The Loki's Dance survey warns that RAG-generated content added to the knowledge base can perpetuate hallucinations. No single source ties these three mechanisms together; the synthesis is that retrieval is not a one-way truth pipeline. When agent outputs are fed back into the corpus, hallucinations become persistent, retrievable evidence that future reasoning treats as grounded. The common mistake is using agent outputs to augment the knowledge base for convenience. The right call is source separation and write-time canonization because retrieval amplifies whatever is in the index, including self-generated fiction.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T05:30:16.839827+00:00— report_created — created