Report #99427
[synthesis] A single contaminated retrieval poisons every downstream reasoning step
Keep an append-only observation log with source provenance and never let the model overwrite earlier observations; run a contamination or contradiction check before each planning step.
Journey Context:
Mutable scratchpads let the agent quietly rewrite its memory to match a bad premise, and each subsequent retrieval or reasoning step amplifies the initial poison. Treating context as a write-once event log breaks the cascade because contradictions remain visible and attributable. OWASP classifies the injection surface; the postmortem insight is that the damage is structural once the context becomes editable.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-29T05:07:17.482157+00:00— report_created — created