Topic
Directed Acyclic Graph
16 episodes
-
2089274302617022464
Masonry and Eyre unpack Iron Giant’s argument that Claude agents aren’t dumb, they’re linear — depth is solved by self-correcting loops, width needs dependency-aware graph orchestration. They trace the generator-verifier pattern, Goodhart failures, and the four load-bearing pieces of a graph, then separate what Anthropic actually documents from what’s speculative, and debate where the pattern helps versus where it adds overhead.
-
Agentic Artifact Creation: Systems, Evaluation, Principles, and Opportunities
A comprehensive survey of agentic artifact creation—systems where AI agents iteratively construct and revise complete deliverables using runtime feedback to redirect work. The paper reviews 259 works (230 systems, 29 benchmarks) across six artifact families (code, documents, images, UI, media, structured data), identifies why direct generation fails for interdependent requirements, and proposes principles for keeping state, verification, and repair tractable as systems scale.
-
DART SD: Diamond topology Aware Retrieval and Tuning for Self Distillation of Multi Turn Tool Calling Agents
Edmund and Geffen discuss the ByteDance/USTC paper DART-SD, which tackles 'topological collapse' in agent distillation. They discuss how moving from linear trajectory imitation to a diamond-topology graph (ISTG) allows student models to learn recovery from errors without destroying their own valid reasoning paths.
-
Graph Engineering in the Era of LLM Agents: From Individual Intelligence to System Intelligence
Pippa and Tyler dig into a survey arguing that once agent tasks need heterogeneous skills, parallel work, verification, and persistent state, the bottleneck stops being model quality and becomes coordination. They frame graph engineering as the move from single-agent cleverness to system-level structure, with explicit graphs for tasks, agents, and runtime state. The conversation stays grounded in shippable workflow design, with Tyler pressing on mechanism and Pippa translating the architecture into product reality.
-
2085024744387092973
Jessica and Cathy dig into a post that tries to boil Claude work down to agents, loops, and graphs. Cathy likes the structure but pushes back on the article’s tendency to make every layer sound universally useful, while Jessica argues the real win is that it gives people a practical ladder instead of vague agent hype.
-
2080668775796314331
Justy and Cody examine the article’s argument that graph engineering is mainly about exposing real dependencies, parallelizing independent work, and adding independent verification. They like the practical core but question the article’s broader claims about speed, graph reliability, and the novelty of the label.
-
Overview: Causal Inference
We keep circling causal inference because the difference between correlation and cause is where a lot of AI gets tricked. We finally slow it down, build the intuition from observational data to interventions, and show why that oxygen-mask problem keeps showing up everywhere.
-
Infrastructure patterns for agentic applications
Justy and Cody unpack why naive HTTP‑wrapped AI agents break in production and walk through three infrastructure patterns—web‑queue‑worker, workflow engines, and a hybrid approach—highlighting idempotency, compensation, and real‑world product impact on teams building long‑running agents.
-
The 2026 07 28 MCP Specification Release Candidate
Miles leads a skeptic's take on the MCP 2026-07-28 release candidate — the biggest protocol overhaul since launch. Stateless core, extensions framework, Tasks redesign, and authorization hardening all land today. Miles is genuinely impressed by the infrastructure work but skeptical about the migration burden on teams who shipped against the old spec. Cooper pushes back on whether the pain is real or just spec-update noise.
-
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 Based Agentic AI with LangGraph: Workflow Pathways for Long Running Stateful Business Processes
Cooper and Miles dig into a practitioner paper on LangGraph as a control-plane for long-running business workflows, not a benchmark toy. They focus on the three recipes in the paper—SQL repair loops, evidence-gated RAG, and human-in-the-loop policy review—and on when a graph is actually worth the extra structure.
-
Andrew Ng 4 agentic steps "from Loops to Graphs from scartch"
Andrew Ng's four-step framework maps agentic design from simple loops (Reflection, Tool Use) through chains (Planning) to graphs (Multi-Agent Collaboration). The central claim: architecture beats model selection—GPT-3.5 in a reflective workflow hits 95.1% on HumanEval vs. GPT-4 zero-shot at 67%. Pippa sees a product win (weaker models ship faster, cost less, iterate tighter). Tyler flags the mechanism: you're not buying smarter; you're buying durable state, typed handoffs, and stopping rules. Both converge that this is the same control-infrastructure pattern they've been tracking—now with a named vocabulary and a staged build path.
-
3 Years of Graph Engineering with LangGraph
Cooper and Miles unpack LangChain's argument that “graph engineering” is not a new magic category, but a practical way to combine deterministic workflow control with agentic flexibility in LangGraph. They dig into where the framing is technically strong, where it risks becoming just another buzzword, and who should actually care.
-
LLM Orchestration Frameworks Compared: LangChain vs. LlamaIndex vs. Raw API Calls MachineLearningMastery
Pippa and Tyler dig into the article’s real argument: these frameworks are not interchangeable, because each one sits at a different layer of the stack. They test the claims against production reality, especially overhead, debugging, and when abstraction stops paying for itself. The episode lands on a practical view: use the lightest layer that actually earns its keep, and don’t confuse orchestration with magic.
-
AI agent tool routing cuts token use 99% | VentureBeat
Cooper and Miles dig into Alibaba's SkillWeaver paper via the VentureBeat write-up, landing on the real claim: tool routing breaks when decomposition vocabulary doesn't match the tool library, and the fix is a retrieval feedback loop that rewrites the plan around actual available skills. They like the systems shape, question some benchmark framing, and agree the practical takeaway is for teams with large tool catalogs, not everyone building simple agents.