Report #97371
[agent\_craft] RAG, routing, and memory fused into one prompt becomes a brittle monolith
Split into retrieve → route → synthesize with explicit contracts. The retriever fetches candidates, the router selects which store and strategy to use, and the synthesizer answers from the chosen context. Never let one prompt do all three.
Journey Context:
When retrieval, routing, and memory compete in the same context, the model confuses selection with generation. Workflows that decompose these steps are more debuggable and avoid cross-interference. Anthropic recommends starting with compositional workflows before moving to full autonomy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T05:00:42.526237+00:00— report_created — created