TRIMLAYER LEARN · EVIDENCE-AWARE CONTEXT
Query-aware RAG context optimization: send evidence, not the entire retrieval set
Retrieval can find relevant documents and still return too much text. Query-aware RAG context optimization narrows the final context to evidence that answers the current question.
TRADITIONAL RAG VS TASK-AWARE RAG
Retrieval finds candidates. Selection decides what the model actually needs.
ILLUSTRATIVE CASE
A security incident question should not receive the entire incident archive.
Suppose retrieval returns deployment notes, rate-limit policy, authentication logs and a security timeline. The question asks why one API key was blocked and whether a rate limit caused it. Task-aware selection should retain the automatic-block thresholds, trusted-integration exception, observed request counts, timestamps and the statement that HTTP 429 responses do not count as failed authentication. Release prose unrelated to those claims can remain recoverable instead of being sent on the first turn.
Example only—not a benchmark claim. Measure the ratio on your own retrieval corpus and include later recovery tokens.
Practical guidance
Retrieve broadly, send evidence
Let the retriever gather candidate passages. Then use the question to select answer-bearing clauses, numeric conditions, definitions and exceptions before constructing the model context.
Practical guidance
Preserve linked evidence
Keep each retained claim connected to its document, section or passage identifier. Citation quality depends on knowing where the evidence came from, not merely retaining similar wording.
Practical guidance
Protect exceptions and negation
A clause such as ‘except trusted integrations’ can reverse the practical answer. Query-aware selection should preserve nearby exclusions, thresholds, dates and temporal conditions.
Practical guidance
Keep omitted context recoverable
When a later turn needs a lower-priority passage, retrieve the scoped original through its evidence identifier instead of replaying the full retrieval set on every request.
Practical guidance
Evaluate the RAG result
Measure critical recall, linked-evidence preservation, answer equivalence, unsafe acceptance, passthrough, recovery and latency. Token reduction alone cannot establish RAG quality.
