{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigtkcqcznru3b6z5ao3j3m6lhspibj47setojiop3yoikguvl52yq",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mmrydlofifr2"
  },
  "path": "/t/multi-turn-rag-for-technical-documentation-using-context-aware-query-rewriting-semantic-caching-is-this-a-sound-approach/172433#post_5",
  "publishedAt": "2026-05-26T20:26:12.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "this sounds to me like 2 issues.\n\n  1. a search issue\n  2. fetch issue.\n\n\n\nim moving to have conversational anchor documents be a part of my conversational flow. meaning that every so often i have the AI Create an Anchor Document of the conversation, as well as a primer that summerizes the conversation. both the Anchor document, and the Primer i have worked to get good formats for what needs to be transcribed.\n\nthe reson for this approach is simple. the lost in the middle problem.\n\npulling from context gets harder and harder for AI as the conversation extends. one of the most notible partersn is Lost in the middle. that is the phenomenon where information from the beginning of a conversation and information from the most recent turns are more retrivable than anything in the middle. because information at the beggining of the conversation and information on the recent turns has greater semantic weight for AI Attention.\nanchor blocks mitigate this by ‘refreshing’ the conversation. now, alot of people know about anchor blocks. i dont know how many know that you can configure anchor block timeing AND content constraints. meaning you can create instructions on what the anchor block should include.\nwhen useing these as PHYSICAL documents, you can work them in to your rag system.\n\nthats part of the fetch issue. once you resolve that now ‘fetch’ is also look for physical files instead of looking for things that are in the ‘murky swamp’ that is the context issue, now you can look at search.\n\nive been working on a ‘fuzzy search’ system, in this system you set some hard parameters, but you build the search instruction to be ‘vague’ when searching, so that not only is it looking for the hard coded tags and such, but it can also pull related topics, incace you have 900 things that it should latch on to, but you can only rememeber 3.\n\nand also a part of search, im working on a unified convention for file names and internal layouts.\n\nwhich makes search even more effective.\n\nand these methods are simple house keeping tecniques.\n\nthey may help in your case.\n\ni think they are related because i to am building a type of 3 phase rag system that works off of physical file storage. and this is part of the approach i am takeing.",
  "title": "Multi-turn RAG for Technical Documentation: Using Context-Aware Query Rewriting + Semantic Caching — Is This a Sound Approach?"
}