Topic
Graph Based Memory Representation
22 episodes
-
Evaluating Graph RAG vs. Standard RAG: A Hallucination Benchmark on Fact Dense Queries MachineLearningMastery
On this Quick Read, Onyx and Echo dig into an article benchmarking a deterministic Graph-RAG system against standard vector RAG, using a synthetic sports dataset designed to stress-test fact extraction. The big question: does layering a knowledge graph actually cut hallucinations when your data is messy, or are we just adding complexity for the sake of architecture? Echo breaks down the technical setup and where the experiment is honest or overclaims, while Onyx pulls it back to who actually needs this in the real world—and where the practical wedge actually is.
-
Gemini at Work 2026: Introducing Gemini agent | Google Cloud Blog
Edmund and Geffen dig into Google Cloud's Gemini agent launch as a control-layer product disguised as a universal assistant: one agent across Workspace, Slack, Microsoft 365, command line, and headless surfaces, with persistent memory, sub-agents, model routing, and enterprise governance. They like the upgrade path and governance story more than the grand 'single agent for work' framing, and they land on the real question: whether companies will trust one cloud-run worker with enough permissions to make the universality claim true.
-
Follow the Entities: A Corpus Map for Agentic Search
Vince and Ava break down CorpusMap, an offline entity layer that gives agentic search a reusable map of a document corpus instead of forcing every query to rediscover the same cross-document links. They focus on the product value, the mechanics of entity pages and document traversal, and whether this looks shippable beyond a paper demo.
-
Adding Temporal Reasoning to Graph RAG: Tracking Fact Freshness and Staleness MachineLearningMastery
Vince and Ava debate a MachineLearningMastery article that adds timestamps and recency decay to Graph-RAG, treating it as a useful retrieval primitive but not a complete truth mechanism.
-
SpeakerMem R1: Speaker Centered Dual Track Memory for Multi Party Dialogue
SpeakerMem-R1 tackles a real gap in long-term memory for group chats: keeping speaker attribution, person/group scope, and evolving state intact instead of flattening everything into a relevance search problem. The episode leans on the paper’s dual-track design, Anchor–Separate–Resolve–Compose query flow, and Writer-R1 training setup, while staying grounded on whether this is actually shippable for multi-party agents.
-
Jev Mem: System One Controlled Agentic Memory for Efficient AI Agents
Jev-Mem is a new agentic memory architecture from UT Dallas that splits memory control into a fast System-One plane and a slower System-Two reasoning plane — cutting query latency by thirty-seven percent and memory construction time by six-point-six times. Vince sees a genuine efficiency unlock for production agent systems; Ava is cautiously impressed but wants to see how it holds up beyond LoCoMo.
-
AI Agents Are Rewriting the Rules of Lateral Movement
A contributed security article makes a strong case that an agent's real blast radius is the chain of identities, credentials, tools, and trust relationships it can assemble, not merely its direct permissions. Edmund sees a practical governance model in purpose-bound agent identity; Geffen agrees with the graph-based risk framing but pushes back on identity being the only meaningful control plane.
-
GraphRAG: A Practitioner's Guide to 6 Advanced Architectural Patterns
Pippa and Tyler dig into a GraphRAG guide that’s really arguing for a more honest question: not “does GraphRAG work,” but “which retrieval shape matches the query shape?” They focus on the production trade-offs between strict graph querying, hybrid vector-plus-graph setups, and when knowledge graphs actually earn their keep.
-
Orchestration is the new challenge for CX in the age of AI agents
Vince and Ava unpack a sponsored VentureBeat piece arguing that orchestration and shared context layers are now the main CX challenge in the age of AI agents. They separate legit architectural points—enterprise ontologies, context graphs, network latency—from marketing around Tata’s Interaction Fabric, and talk about who actually needs to care and what changes in practice for CX and IT teams.
-
Making the Knowledge Layer a Graph You Actually Traverse
Vince and Ava examine a redesign of a persistent knowledge layer that retires keyword-based routing in favor of always-fused retrieval, graph traversal, bitemporal edges, discovered contradictions, and stronger entity resolution.
-
Vector RAG vs Graph RAG: Which Fits Best? | EM360Tech
Pippa and Tyler break down the real-world choice between Vector RAG and Graph RAG for enterprise AI: Vector RAG shines in straightforward retrieval but falters when the answer lives across relationships, while Graph RAG brings structure and richer answers—for a cost. The takeaway? Hybrid approaches are quietly becoming the practical default.
-
Kimi Agent Swarm's Real Trick: 300 Agents Building a Connected Context Graph
Vince and Ava dig into a post arguing that Kimi Agent Swarm’s real trick is not 300 parallel agents by itself, but turning their outputs into a connected context graph that compounds over time. They test the claim against their running thesis about harnesses, receipts, and selective structure.
-
Stop graphing everything: When GraphRAG actually beats vector RAG
Pippa and Tyler dig into a fresh GraphRAG piece that argues graphs only beat vector RAG when the question needs multi-hop reasoning, global sensemaking, or summary across an interconnected corpus. They walk through the mechanism, the benchmark evidence, the cost caveat, and the practical hybrid answer without pretending graphing everything is the move.
-
Overview: Directed Acyclic Graph
We finally slow down on directed acyclic graphs, or D A Gs, because this one quiet structure keeps showing up under workflows, agents, build systems, and half our control-stack arguments. We make it click as a map of prerequisites: arrows for order, no loops, and a scheduler that can see what can run now.
-
Overview: Graph based Memory Representation
We finally slow down and explain graph-based memory representation, the thing we keep gesturing at whenever agent memory, receipts, and relationship-aware retrieval come up. We use one corkboard mental model to make nodes, edges, traversal, and the real trade-offs feel less mystical.
-
Graph Engineering Is Replacing RAG at Microsoft, Stanford, and Anthropic
A viral claim that Graph Engineering has displaced RAG at major AI labs, and what that actually means in practice.
-
Building Knowledge Graphs with Claude: A Prompt Based Engineering Playbook
Anthropic's knowledge-graph engineering playbook replaces classical NLP pipelines (trained NER, relation classifiers, entity-resolution heuristics) with a sequence of Claude API structured-output calls. The entire extraction-resolution-assembly-querying loop becomes prompt-based, scaling from Haiku (high-volume extraction) to Sonnet (reasoning). The graph serves multi-agent systems as shared memory, grounding layer for evaluator-optimizer loops, and persistent world model across sessions. The paper maps this onto Anthropic's five canonical agent patterns and reports precision/recall against a gold set.
-
How to Implement a Unified Memory from Scratch
Jessica and Cathy dig into a new post that walks through building a unified agent memory from scratch using knowledge graphs and MongoDB, unpacking what it actually takes to wire memory into a real agent harness. They tease apart where the post’s blueprint shines, where it overreaches, and who on earth should actually roll their own instead of reaching for an off-the-shelf tool.
-
AI agent memory: MRAgent cuts token use up to 27x | VentureBeat
MRAgent from NUS replaces static retrieve-then-reason memory with active reconstruction during reasoning, cutting token use 27x over competing frameworks. The system treats memory as an interactive graph where agents dynamically refine retrieval paths based on intermediate evidence, using a three-layer Cue-Tag-Content structure and automated ingestion pipelines.
-
Perplexity Launches Brain: A Self Improving Work Memory for Computer
Justy and Cody dig into Perplexity Brain, a new work-memory system for Computer that learns from what the agent did, not just who the user is. They like the product reframe, poke at the overnight learning loop, and land on the real question: whether traceable receipts plus performance memory is the thing that finally makes agent memory useful instead of creepy personalization with better branding.
-
Skill Graphs > SKILL
Jessica and Cathy dig into Heinrich's 'Skill Graphs > SKILL.md' post — the argument that a single skill file is a dead end for complex domains, and that wikilink-connected graphs of small markdown files let agents navigate knowledge rather than just receive it. They work through what's genuinely new here versus repackaged context engineering, and whether the arscontexta plugin is a real workflow change or a clever demo.
-
The No BS Guide to Build a Context Graph
Najmuzzaman's 'No BS Guide to Build a Context Graph' lays out how a production context infrastructure moves beyond CRM data to capture decision traces, organizational patterns, and lived heuristics. The real breakthrough is surfacing context and patterns that aren't captured in playbooks, making organizational intelligence accessible and explainable. The hard technical work: entity resolution, permissioning, and evolving patterns transparently.