What this video shows
Feig uses customer sentiment questions to separate direct lookups from searches across large historical datasets. A live API can retrieve one known record, while a synchronized index supports filtering and semantic retrieval across many records. A router chooses the source, and a summarizer combines the evidence with company-specific skills and memories.
Learnetto finds the live-versus-synced decision useful, but the term context graph is broader than the graph database definition in this talk. The speaker presents a vendor architecture rather than comparative evidence. Teams should model permissions, freshness, deletion, provenance, and source conflicts before choosing storage or integration products.
Airbyte documents a similar distinction in its Context Store and live connector model, including OAuth and searchable replicas. Use the MCP architecture documentation to understand what the protocol provides before adding a separate context layer.
What you will learn
- Use live calls for current known records and synchronized search for broad historical or semantic questions.
- Store the source, retrieval time, permissions, and invalidation conditions with derived context.
- Express company definitions as reviewed skills or rules so users can inspect what terms such as active customer mean.
- A router needs evaluation cases for stale copies, missing permissions, conflicting records, and unsupported queries.
How to apply this safely
- List the top agent questions and classify each as direct lookup, filtered search, semantic search, or derived analysis.
- Choose the authoritative source for each field and specify synchronization, deletion, and permission behavior.
- Return citations and timestamps with every retrieved record or generated summary.
- Test known-record lookups, corpus-wide questions, revoked access, stale data, and disagreement between live and synchronized sources.
Important limitations
- The speaker is a Merge co-founder, and the final architecture supports Merge products. The talk does not compare retrieval quality, latency, or cost with other systems.
- A synchronized copy creates security, retention, residency, and deletion obligations. The video gives a conceptual architecture rather than a complete governance design.
Sources to check
- Airbyte Agent MCP Official example of authenticated live connectors and a synchronized context store.
- Model Context Protocol architecture Official overview of MCP clients, servers, tools, resources, and prompts.
Continue learning on Learnetto
Best RAG courses for developers
Study ingestion, retrieval, reranking, grounding, and evaluation.
Best AI agent courses
Place context routing inside the wider agent loop.
AI evals guide
Test retrieval, permissions, freshness, and answer grounding.