← All IntelClip / AI AgentsFour takeaways for agentic architecture
From Why We Killed Our Multi-Agent Pipeline — Subbiah Sethuraman and Abhilash Asokan, ZS Associates · ≈13:45
Compresses the whole postmortem into four transferable rules: don't encode human org constraints into topology, split deterministic from agentic, one agent owns reasoning, graph is a control plane.
What’s in it
- Compresses the whole postmortem into four transferable rules: don't encode human org constraints into topology, split deterministic from agentic, one agent owns reasoning, graph is a control plane.
Clip transcript
>> So, just to wrap it up, key takeaways. First thing is I think we should not be introducing human constraints or design constraints into architecture. I think let the architecture be derived actually. Number one. Second, I think any complex workflows will have deterministic parts and agentic parts. Don't let agents actually run the deterministic part, right? So, I think we need to break break that off. The third, need to have one agent, right? Which owns the reasoning end to end, right? This agent can actually take the call to use sub agents, tools, skills to actually spawn off other other tasks basically, right? But you need one agent to own the the reasoning. And the last, probably the most important, I think graph cannot be treated just as a lookup layer. I think graph has to be treated as a control plane which the agent uses to navigate and takes the next decisions basically.
Comments
Sign in to comment.
Loading comments…