Skip to content
aiqbench takeAI Products

aiqbench analysis

This presentation details how knowledge graphs provide the structural foundation necessary to transition AI systems from simple retrieval tasks to complex reasoning capabilities within production environments. The author outlines specific architectural patterns—such as context bundling and decision provenance—that enable agentic systems to maintain reliability, optimize token usage, and ensure code-level transparency. By integrating graph-based data structures with software engineering best practices, developers can build robust agent ecosystems that go beyond basic RAG implementations.
Source coveringInfoQ
What this isA model's reading of the article and related coverage, written for aiqbench. Not the publisher's words.

Presentation: From Retrieval to Reasoning: Building Production-Ready Agentic AI Systems with Knowledge Graphs

InfoQ38 min read

Cassie Shum discusses why knowledge graphs serve as a critical foundation for agentic systems. Moving beyond basic RAG, she explains 4 practical architectural patterns: context bundling, decision provenance, code as truth, and agent visibility. She demonstrates an engineering harness built on a knowledge graph to streamline feedback loops, optimize token usage, and maintain system reliability. By Cassie Shum

Cassie Shum: Today I'll be talking about knowledge graphs and retrieval to reasoning, and some of my experiences, and what I know and what I've been working on for the past few years. Let's go ahead and just start talking about me just so you can get some context about my background and actually why I care about all of this. Today, I actually spend a lot of time building and running agentic systems. I just can't get enough of it. It's like the gambler thing. Every time I hear that ding, I'm like, ok, what's next? What's next? That's actually how I started off 20-plus years ago. I started off, as many of you have, as an engineer, as a coder, and I got really excited about solving problems, creating applications, getting customers to see what you've actually built. Then, as I went through my career at Thoughtworks and a few other places, working with customers as a consultant, I turned into this hand wavy person, talking about microservices and architecture and all of these things. I accidentally, but probably somewhat intentionally, got away from the codebases and started managing all these teams and organizations on how to create…

Excerpt shown under the publisher's RSS terms · 200 words · full text and figures are on the publisher's site

Related coverage