Beyond RAG: A Relational Context Engine That Cuts Token Burn — Unblocked
The talk introduces the concept of a Context Engine, arguing that modern AI agents require more than simple Retrieval-Augmented Generation (RAG) or vector search. A Context Engine gathers and structures 'institutional knowledge'—including PRs, Slack threads, and incident history—to provide 'grounded context.' This approach allows agents to answer complex, structural, and temporal questions (e.g., 'Which PRs did I merge last week?') and significantly reduces operational costs by providing highly focused context bundles.
Key takeaways
-
Context Engines vs. Vector Search
11:51
Vector search excels at semantic content retrieval (finding related documents), but it fails at structural questions that require querying relationships, temporal data, or specific system metadata. A Context Engine addresses this by synthesizing data from disparate sources (PRs, Notion, Slack).
-
Cost and Accuracy Improvement
6:00
Demonstrations showed that attaching a context engine resulted in a 50% reduction in API costs and enabled complex debugging, such as tracing a regression to a specific model switch (Opus 48 vs Opus 46).
-
The Structured Query Pipeline
17:11
The core process involves turning natural language queries into safe, validated database queries. This requires five key steps: Automatic Schema Discovery, Identity Resolution, Query Validation, Retries, and Full-Text Search.