<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Retrieval on Tech Foundations</title><link>https://valery.tech/ai-engineering/retrieval/</link><description>Recent content in Retrieval on Tech Foundations</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2014-2023</copyright><atom:link href="https://valery.tech/ai-engineering/retrieval/index.xml" rel="self" type="application/rss+xml"/><item><title>Conceptual Alignment</title><link>https://valery.tech/ai-engineering/retrieval/conceptual-alignment/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/retrieval/conceptual-alignment/</guid><description>&lt;h1 id="conceptual-alignment-and-contract-discipline-in-rag-systems"&gt;Conceptual Alignment and Contract Discipline in RAG Systems&lt;/h1&gt;
&lt;p&gt;A recurring problem in RAG system design is conceptual misalignment. Different parts of the system often use the same term for different artifacts, or collapse distinct artifacts into a single object.&lt;/p&gt;</description></item><item><title>Model</title><link>https://valery.tech/ai-engineering/retrieval/model/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/retrieval/model/</guid><description>&lt;h1 id="model-of-context-augmented-task-systems"&gt;Model of Context-Augmented Task Systems&lt;/h1&gt;
&lt;p&gt;This ontology and models defines a systems-level view of context-augmented task execution. Its purpose is to separate concepts that are often collapsed in retrieval-augmented systems: the user&amp;rsquo;s observable request, the task the system infers from that request, the context required to complete the task, and the source-directed queries or actions used to obtain that context.&lt;/p&gt;</description></item><item><title>Model Representation Design</title><link>https://valery.tech/ai-engineering/retrieval/model-representation-design/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/retrieval/model-representation-design/</guid><description>&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Task need&lt;/th&gt;
 &lt;th&gt;Useful representation&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;Find exact term or identifier&lt;/td&gt;
 &lt;td&gt;lexical index, keyword field, exact-match metadata&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Find semantically related policy or explanation&lt;/td&gt;
 &lt;td&gt;dense vector representation, hybrid search&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Find a person, product, account, or project&lt;/td&gt;
 &lt;td&gt;entity index, normalized metadata&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Answer from tables&lt;/td&gt;
 &lt;td&gt;table objects, extracted rows, schema-aware search&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Traverse relationships&lt;/td&gt;
 &lt;td&gt;graph representation&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Verify authority&lt;/td&gt;
 &lt;td&gt;source metadata, ownership, approval status, policy hierarchy&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Check freshness&lt;/td&gt;
 &lt;td&gt;timestamps, version fields, update history&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Cite evidence&lt;/td&gt;
 &lt;td&gt;passage-level chunks with provenance&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Summarize large documents&lt;/td&gt;
 &lt;td&gt;section summaries, document outline, hierarchical chunks&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;A stronger framing would be:&lt;/p&gt;</description></item><item><title>Reframing</title><link>https://valery.tech/ai-engineering/retrieval/reframing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://valery.tech/ai-engineering/retrieval/reframing/</guid><description>&lt;h1 id="beyond-rag-task-to-context-alignment"&gt;Beyond RAG: Task-to-Context Alignment&lt;/h1&gt;
&lt;p&gt;Goal: We should stop treating RAG as the architecture and instead treat it as one pattern within task-to-context systems.&lt;/p&gt;</description></item></channel></rss>