Unverified50% confidenceSolutionExact time
In RAG scenarios, the retrieved context changes with every query, and if it is placed early in the prompt it breaks cache hits for subsequent content, so the static system prompt is usually placed first to benefit from caching, with dynamic retrieved document chunks placed later.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedTraditional retrieval-augmented generation (RAG) approaches are passive, only retrieving relevant content when a query is received, triggered externally, with the model itself not deciding what or when to retrieve.75% similarUnverified采用RAG而非直接注入全文，通过检索最相关片段能降低上下文长度并将关键信息保持在上下文近端，缓解注意力分散和指令衰减75% similarUnverifiedIn RAG scenarios, concatenating retrieved context documents into the Prompt causes a sharp increase in input tokens, and exceeding the context window limit results in API errors or truncated input.74% similarUnverifiedMost enterprise RAG systems bake access control into the vector index at the embedding stage, treating permissions like content freshness, so that revoked access rights can still return results through retrieval, forming a security lag window.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1037655API
curl https://kongchang.com/api/v1/knowledge/claims/1037655MCP
get_claim(id=1037655)