A few weeks ago, Hemant Mohapatra, partner at Lightspeed and I started discussing the evolution of agentic systems and realized there wasn’t a clear, canonical architecture to address the complexities of scaling these systems. So we set out to explore: 1/ What are the key infrastructure components required to enable agentic systems at scale? 2/ What role does UX design play in ensuring adoption and reliability? 3/ How can a multi-agent system handle real-world use cases like customer support? 4/ What are the opportunities for builders and challenges for enterprise adoption? How to think about differentiation? This article, "Endless Homers, Infinite Agents", is the first part of a series where we tackle these questions and share actionable insights. Feedback and comments welcome —hope you enjoy reading it as much as we enjoyed writing it! Link to the article: https://lnkd.in/g_q8XkcT
A few weeks ago Meenal Nalwaya who heads up multimodal LLMs at Meta and I were chatting about what is going on in the world of agentic infra globally. There have been a bunch of opinions on what agents are, what they can do, but there was no clear canonical architecture that was emerging. Even doing something as basic as a personal agent to book "a flight ticket to SFO tomorrow" needs the agent to know what "today" is, where "here" is to book something from here to SFO, my flight + seat + meal preferences, my FF number, my ID & credit card info, then once booked, schedule an uber ride, get my boarding passes & place it on my calendar, and ensure a pickup & a hotel once I land, and so much more. A simple task like this has so, so many complexities. We felt we needed to dig into what is the architectural framework needed to solve some of this. We also felt that this problem needs a 2-sided approach - you can build a bicycle but then you also need the roads to build bicycle lanes or it doesn't work. While we believe this utopian world where agents can book us a flight, a car, a hotel, is still not here yet, we wanted to write a series of articles to help us think about the opportunities and challenges ahead. This is the first part of a series of articles, feedback & comments welcome - link in the first comment - and hope you enjoy the Homer Simpson references :) part 1: "Endless Homers, Infinite Agents":
Few additional Design criteria How can precise models be released at fast pace when the data might not sometimes be always readily available? How can compliance and data privacy requirements be met satisfactorily [day 0] what would be efficient methods that can be leveraged to quickly onboard customers data? How to address enterprise SLAs and general AI readiness when there is problems around, (1) Data Scarcity for trainings and operations (2) Issues around Data Quality (3) Domain specific variableness (4) Data privacy (5) Data security (6) Hallucinations etc. The deployment of AI agents also can raise ethical questions, including concerns about bias, transparency, and accountability etc. E-W Agent firewalling, micro-segmentation is much needed ; Performance monitoring, HA, orchestration complexity aspects Agents' security model needs work — how to detect & prevent rogue agents, misconfigurations, inadvertent data exposures, malware injections, agent hijacking, zombie resource consumptions (DOS attacks), credential abuse etc. A full stack agent level observability — requiring support for Multi tools, diverse environments, drifting states [aka a need for Agents LLMOPs for observability & explainability] Agent ROI metrics
Hemant Mohapatra can we connect to explore VC funding from lighspeed.
Way to go Meenal Nalwaya and Hemant Mohapatra !!
Akshay K
Great stuff Meenal Nalwaya
CEO at DevRev; Board Member at Adobe; Investor & Co-founder at Nutanix
3wThe more things change, the more they remain the same. Would’ve loved to see a comparison with the workflow engines of the yore. - tools are rule-based automations — will the old workflow engines work? If we try to retrofit them, we will have too many “callouts” to model-based nodes that do probabilistic work like cluster-classify-deduplicate-deflect-route-attribute-generate-… - the role of no-code and low-code tools for building hybrid automations that mix and match rules and model nodes - restartability, checkpointing, write-ahead logging, authorization, loop detection, deadlock detection, quotas, resource management… there are a gazillion enterprise-grade requirements for reliability, diagnosability, and availability. - aren’t the things below ‘skills’, not agents?