Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Graph engineering isn't monolithic; it involves choosing between two architectures. "Org graphs" are stable systems for ongoing, recurring processes with long-lived agents and fixed dependencies. In contrast, "work graphs" are dynamic and ephemeral, designed for specific projects where agents and their interactions can be created, adapted, or destroyed as the task evolves.

Related Insights

To build a useful multi-agent AI system, model the agents after your existing human team. Create specialized agents for distinct roles like 'approvals,' 'document drafting,' or 'administration' to replicate and automate a proven workflow, rather than designing a monolithic, abstract AI.

Graph engineering isn't a single concept. Knowledge graphs map relationships within data (customer to company), while agent graphs design multi-step AI workflows (planner to researcher to skeptic). Understanding this distinction is key to applying the right AI approach for a given problem.

True Agentic AI isn't a single, all-powerful bot. It's an orchestrated system of multiple, specialized agents, each performing a single task (e.g., qualifying, booking, analyzing). This 'division of labor,' mirroring software engineering principles, creates a more robust, scalable, and manageable automation pipeline.

An AI agent uses an LLM with tools, giving it agency to decide its next action. In contrast, a workflow is a predefined, deterministic path where the LLM's actions are forced. Most production AI systems are actually workflows, not true agents.

The next evolution of agentic work involves massive, collaborative swarms of AIs working together. Current tools like GitHub, designed for human workflows with a single master branch, are ill-suited for this paradigm. The future will require new, agent-native platforms, possibly resembling social networks, to manage thousands of parallel experiments and collaborative branches.

Complex AI development uses a pool of specialized agents. Like ants building a hill, some are workers, some are managers, and some review and discard bad code. This collaborative, layered system produces emergent results without a single orchestrator.

To decide between a deterministic workflow and a flexible agent, analyze the current manual process. If the task involves numerous 'if-then' conditions and decision points, an agentic system is likely the more maintainable and effective solution.

Moving beyond "loop engineering" which programs a single agent's iterative process, "graph engineering" designs the entire system of interaction between multiple agents, tools, and humans. It defines the "agentic organization"—specializations, data flows, and failure protocols—making the entire AI-powered workforce programmable, not just individual tasks.

The goal of graph engineering isn't creating the largest diagram of AI agents. More agents often lead to more noise and coordination overhead. The most effective graph is the smallest one that significantly improves work quality by separating workers from checkers and adding human approval at critical junctures.

Unlike traditional ML pipelines with predefined steps (DAGs), AI agents operate as dynamic, unrolled graphs. Their workflow is a tree-like structure of LLM and tool calls determined at runtime, requiring systems that can handle real-time graph definition rather than static compilation ahead of time.

Agentic Systems Require Differentiating Stable "Org Graphs" from Dynamic "Work Graphs" | RiffOn