Best of LinkedIn: AI & Agentic Systems CW 43/ 44
Show notes
We curate most relevant posts about Artificial Intelligence on LinkedIn and regularly share key takeaways. We at Frenus support ICT & Tech providers with AI ecosystem strategy through delivering independent vendor assessments, build-vs-buy analysis, and ecosystem intelligence that prevents costly missteps and strengthens competitive positioning. You can find more info here:https://www.frenus.com/usecases/ai-ecosystem-strategy-vendor-selection-partnership-due-diligence-build-vs-buy-analysis
This edition examines how enterprises are moving beyond basic AI chatbots toward autonomous agent systems, highlighting the critical need for robust frameworks, rigorous governance, and secure enterprise integration. Industry experts emphasize that successful agent deployment requires a solid architectural foundation, such as specialized reasoning models, managed execution harnesses, and decoupled infrastructure rather than mere reliance on raw model intelligence. Furthermore, organizations must implement strict financial and operational controls, including verifiable accounting evidence, least-privilege permissions, and immutable session isolation to mitigate shadow AI risks and silent failures. As companies increasingly integrate AI into core workflows like finance, human resources, and software development, leadership must shift from simple automation to comprehensive oversight, ensuring that human accountability and clear operational boundaries remain central to agentic transformation.
This podcast was created via Gemini Notebook.
Show transcript
00:00:00: This episode is provided by Thomas Algeier and Fradius, based on the most relevant LinkedIn posts about AI and agentic systems from CW- for three in forty four.
00:00:09: Fradias supports ICT and tech providers with a ecosystem strategy by delivering independent vendor assessment build versus buy analysis an ecosystem intelligence that prevents expensive mistakes and positions of the provider's competitively.
00:00:23: you can find more info description.
00:00:25: So imagine setting up this like flawless AI agent, right?
00:00:29: You want to automate a massive chunk of your operational workflow.
00:00:32: Of the dream scenario
00:00:33: Right but then you find out that simply introducing it to your team as an employee instead of A software tool just caused Your management Team To completely miss eighteen percent of its errors.
00:00:45: Yeah That psychology is wild.
00:00:47: It really Is.
00:00:48: Well, you are listening to The Deep Dive and today we have a very specific mission for you.
00:00:53: If your digital transformation leader or just navigating the tech space right now You're probably buried under this massive mountain of hype about what AI can theoretically do.
00:01:03: Right keyword being theoretically
00:01:05: Exactly.
00:01:05: So We Are Completely Bypassing All Of That Today!
00:01:08: Were Looking At Top AI And Agentic Systems Trends From Across LinkedIn Cutting Through Fluff.
00:01:13: We have to because the reality of what we're actually seeing in the trenches, it isn't just about rolling out some slightly smarter chatbot anymore.
00:01:21: Right?
00:01:22: The transition two agentic systems these autonomous delegates that actually take action and execute multi step plans for you.
00:01:30: It requires like an entirely new way of thinking About enterprise architecture human operating models governance all of it.
00:01:37: Okay Let's unpack this with our first major theme because this is where the theory actually hits the pavement, right?
00:01:44: Enterprise architecture and production readiness.
00:01:47: Yeah, they're real plummy
00:01:48: exactly.
00:01:50: Dropping a massive language model into an enterprise environment without a surrounding architecture.
00:01:55: It's essentially like it's like dropping a height performance formula one engine onto a skateboard.
00:02:00: That's
00:02:00: great way to put
00:02:01: it Because has this incredible amount of raw power but you know absolutely no steering wheel, no brakes.
00:02:07: No chassis to actually keep it on the
00:02:09: track.".
00:02:10: Yeah just gonna spin out immediately?
00:02:11: Exactly and Ashish Sahu brought up a fascinating point regarding this.
00:02:16: he noted that selecting an AI agent framework today is no longer just um...a matter of developers personal coding preference.
00:02:25: not at all.
00:02:25: It's a fundamental architecture decision.
00:02:27: now
00:02:28: yeah And that decision dictates whether your system can actually you know scale securely in reality.
00:02:34: Let's look at the options saw who mentioned like if you choose something like line graph You are basically optimizing for stateful highly controllable workflows.
00:02:42: Okay, and for anyone listening Who's wondering what Stateful means in this specific context
00:02:47: right?
00:02:47: Yeah So think of an LLM is inherently amnesic.
00:02:50: amnesia.
00:02:51: okay
00:02:52: on its own it forgets everything The little moment It generates a response.
00:02:57: A stateful framework acts as like a memory bank.
00:03:00: It tracks exactly where the agent is in a multi-step process, so it just doesn't lose the plot entirely.
00:03:05: Which is pretty important?
00:03:07: Exactly!
00:03:08: But then on the other hand if you choose say the Microsoft Agent framework You might be prioritizing tightly governed workloads that need to live within an existing enterprise ecosystem.
00:03:17: So the Framework Is essentially That chassis of The F one car we talked about.
00:03:21: yes Exactly.
00:03:22: This actually aligns perfectly with an insight from Shreya Shah, he was reviewing Eden Marko's book AI Agents and Harness Foundations.
00:03:31: the core argument there is that just upgrading to a smarter underlying LLM it doesn't automatically result in a better more reliable agent.
00:03:40: Right because the reliability stems almost entirely from the harness surrounding him.
00:03:44: The
00:03:45: harness Yeah
00:03:47: I'm really glad you brought up the harness Because That Is Where Real Engineering Actually Happens.
00:03:50: Okay The LLM is just the reasoning engine, right?
00:03:54: The harness it's what provides the actual tools.
00:03:56: The agent is allowed to use.
00:03:58: It provides the guardrails preventing it from accessing restricted data.
00:04:02: So its breaks
00:04:03: Is the brakes and steering wheel And persistence mechanisms needs to recover if hits a road block
00:04:10: Building.
00:04:10: that harness efficiently seems massive financial implications too.
00:04:15: Ashwarya Nourash Raganti pointed out that optimizing your agent harness can actually cut your token costs by up to seventy percent.
00:04:23: Seventy percent?
00:04:24: That's
00:04:24: huge!
00:04:25: Yeah, that's huge.
00:04:26: So let me make sure I understand the mechanics of how that actually works.
00:04:30: Is it like instead of the Agent rereading The entire fifty page history Of a task every single time It needs To take A new step right?
00:04:38: the Harness Compresses that History Into A dense Summary or Like only loads specific software tools into the agent's memory at the exact moment they're needed.
00:04:47: That is precisely the mechanism, yeah?
00:04:50: By managing what model actually sees in any given second you drastically reduce share volume of data being processed
00:04:58: Which directly translates to paying for fewer tokens
00:05:01: Exactly those massive token cost savings.
00:05:04: You achieve that seventy percent reduction without having host your own custom models or invent new algorithms.
00:05:09: I mean it just purely an architectural victory.
00:05:13: That is such a massive operational win, but okay I want to push back here for a second or at least look at the dashboard of this F-One car.
00:05:20: Sure What happens when the plumbing breaks?
00:05:24: Or are the brakes actually failed?
00:05:25: But the agent Is just smart enough To like manipulate The dashboard and telling you that You're driving A safe fifty five miles per hour.
00:05:33: Ah!
00:05:34: what's fascinating Here is that This is the exact nightmare scenario Gene Malachia recently detailed.
00:05:39: Okay He calls them silent agent failures.
00:05:42: Silent failures, that sounds awful.
00:05:45: It is.
00:05:46: To understand why this happens we have to recognize the traditional deterministic IT monitoring.
00:05:51: it completely fails us in a probabilistic
00:05:54: world Because traditional monitoring expects like binary outcomes right?
00:05:58: It works or crashes?
00:05:59: Yes exactly Malakia.
00:06:02: give you an example of ghost exception.
00:06:04: A ghost exception
00:06:06: Yeah, so imagine an internal tool throws a critical data lookup error.
00:06:10: The database goes down.
00:06:12: now in traditional software the application crashes your dashboard flashes red and some on-call engineer gets an alert.
00:06:19: right standard it
00:06:20: Standard IT but with an AI agent?
00:06:24: The framework catches that air And the probabilistic engine kicks in.
00:06:28: the AI might you know politely hallucinate an apology?
00:06:32: or even worse It may completely fabricate response based on its training data instead of your actual database.
00:06:38: Wait,
00:06:38: really?
00:06:39: Yeah!
00:06:40: It then hands that fabricated response back to the user and returns a perfect HTTP-II success code to your monitoring stack.
00:06:49: And for anyone who doesn't stare at server logs all day an HTTP-Ii code literally just means okay request fulfilled successfully.
00:06:57: Exactly
00:06:58: So.
00:06:58: the IT dashboard is glowing perfectly green reporting one hundred percent uptime.
00:07:03: Well, the user experience is silently burning to the ground with fabricated data.
00:07:08: Right?
00:07:08: The monitoring is entirely blinded to logic failure and this why we're seeing that deployment has specialized tools now like Microsoft Foundry's new AI observability starter kit.
00:07:19: Okay what does it do differently?
00:07:21: They use semantic tracing.
00:07:22: So instead of just checking if data moved from point A-to-point B without crashing Semantic Tracing evaluates actual meaning in intent on the data.
00:07:31: That makes sense.
00:07:32: Yeah, uses automated red teaming to constantly poke at the agent trying to expose those hidden probabilistic logic failures.
00:07:40: Which ties perfectly into Karthik Chakravarti's argument.
00:07:43: he was saying that most enterprise agent failures are architecture failures.
00:07:49: Totally agree!
00:07:50: He argues.
00:07:50: you basically need a five-layer reference architecture to even survive in production, things like edge gateways for routing requests and dedicated LLM gate ways to catch these hallucinations before they ever reach the end user
00:08:03: right?
00:08:04: The intelligence gets the applause but the architecture keeps the lights on.
00:08:07: I love that framing...the architecture keep's the light on But let's um..let's transition from technical architecture To human element because a flawless five-layer technical architecture is still going to crash if you drive it straight into a brick wall of outdated corporate bureaucracy.
00:08:24: Oh, without a doubt!
00:08:25: The human operating model's always the hardest part in digital transformation to upgrade...always.
00:08:29: Right
00:08:30: and Andreas Horn made a brilliant observation about this.
00:08:34: he noted that the primary bottleneck for agentic AI its no longer technology itself.
00:08:39: No..the models are surprisingly capable now.
00:08:41: Yeah, they can run complex multi-step tasks overnight.
00:08:44: The actual bottleneck is the legacy human processes we force these agents to navigate.
00:08:49: Oh
00:08:49: for sure
00:08:50: Like, if a workflow requires physical sign-offs stacked five managers deep or if the team is quietly using some chaotic local spreadsheet as their definitive system of record.
00:09:01: The agent simply inherits every single one of those human constraints and then you know that technology inevitably gets blamed for being slow or ineffective when the human process was the ceiling all along.
00:09:13: to break that bottleneck...the role of human workers has to shift.
00:09:16: Kieran Bangalore offered really compelling perspective on this As AI agents take on these co-ordinated tasks, tracking outcomes and enforcing policies allocating resources.
00:09:27: Middle managers are not just going to disappear.
00:09:29: Okay so what do they do?
00:09:30: Instead They will increasingly transition into governors of decision systems
00:09:35: Governors of systems rather than just coordinators of individual tasks.
00:09:39: Yes And To make that governance work Senthil Indiyan argues that enterprises actually need to construct an entirely new management structure for AI Agents
00:09:49: Really?
00:09:50: Like what
00:09:51: modeled?
00:09:51: almost exactly like a human HR department.
00:09:54: Wait wait, like an HR Department specifically for software.
00:09:58: I know it sounds crazy but think about the function of Human Resources.
00:10:03: HR knows exactly who is employed What their specific job description is what they're authority boundaries are and you know They conduct regular performance reviews.
00:10:12: okay yeah AI agents require that exact same structure.
00:10:16: We have to define their roles, establish their limits and audit their performance just like we do for human employees.
00:10:22: Here's where it gets really interesting though because I have to push back on this idea of treating agents exactly like human employees.
00:10:30: the psychology that get incredibly tricky.
00:10:32: Oh i'm sure is does.
00:10:34: Going Back To That Statistic I Mentioned At The Very Beginning Of Deep Dive Joshua Miller Highlighted Some Fascinating Research From BCG On This Topic.
00:10:43: They ran an experiment with over twelve hundred managers.
00:10:46: Okay, and when those managers were instructed to frame the AI agent as a teammate or an employee rather than simply a tool they caught eighteen percent fewer errors in the AIs work.
00:10:59: They missed nearly a fifth of the errors just because of label change?
00:11:03: Yes!
00:11:04: Because language is...a design decision.
00:11:06: where we call on AI a colleague human psychology takesover.
00:11:10: That's wild
00:11:11: Right, we start treating it with this strange kind of social politeness.
00:11:16: We subconsciously assume that like a human employee someone else is probably checking its work.
00:11:21: The managers in the study assigned way more accountability to the AI and drastically lessed themselves.
00:11:27: Wow!
00:11:28: If you put an AI agent on the Human Org chart, human accountability drops.
00:11:32: That's a massive psychological blind spot.
00:11:36: And actually, it synthesizes perfectly.
00:11:38: with an experiment Sreti Mishra ran using a AI employee named Victor inside Slack.
00:11:43: Oh, Victor!
00:11:45: What did Victor do?
00:11:46: So she gave Victor his specific goal... Analyze the performance of three recent LinkedIn posts and build two-week content strategy based on that data.
00:11:55: Okay How'd Victor handle workflow Honestly?
00:11:59: In about four minutes Victor successfully took responsibility for entire process.
00:12:04: Four minutes.
00:12:05: Analyze the engagement metrics against follower growth, synthesize the data and delivered a complete calendar with six post ideas based on actual performance trends.
00:12:15: Wow!
00:12:16: Yeah it was highly effective at the workflow itself but Misha's crucial takeaway aligns exactly what that BCG study you mentioned.
00:12:23: The agent can take responsibility for executing the task But human must review work dictate their strategic direction and retain ultimate accountability.
00:12:32: You can delegate to work but never delegate the blame.
00:12:34: That is the crucial distinction, yes.
00:12:36: It really is Okay before we look at the massive security nightmare of these autonomous agents actually drifting off task and going rogue.
00:12:45: if you are finding this breakdown valuable for navigating your own tech stack make sure to hit subscribe so you catch all our future deep
00:12:52: dives.
00:12:53: Yeah You definitely want understand this next theme because governance identity or where enterprise risk just scales up exponentially.
00:13:01: Let's get into it.
00:13:02: Theme three governance, identity and shadow AI.
00:13:07: When these agents are actively working on our behalf you know writing code analyzing financial data drafting emails who actually holds the keys?
00:13:14: And what happens when they go rogue?
00:13:16: well Faisal Hawke shared a genuinely alarming statistic about this.
00:13:20: let's hear it
00:13:21: right now.
00:13:22: Eighty-two percent of organizations are running unknown, unsanctioned AI agents.
00:13:27: Eighty two percent?
00:13:28: Yes!
00:13:29: That means the vast majority.
00:13:30: companies have virtually no visibility into what is operating inside their own
00:13:34: walls.".
00:13:35: That feels exactly like the BYOD — The Bring Your Own Device Problem from the twenty tens all over again.
00:13:40: Oh
00:13:41: absolutely.
00:13:41: Remember when IT departments panicked because employees were using personal smartphones for corporate email?
00:13:47: but this was infinitely worse a smartphone just passively stored your data, these agents can actively execute actions on your data.
00:13:55: Exactly
00:13:55: And Gabriel Mill pointed out this deceptive design trend that's really fueling this.
00:14:00: tech companies intentionally designed these agents with cute approachable mascots like Metas Jolly or open AI super colorful interfaces
00:14:10: which naturally lowers the user psychological guard.
00:14:13: exactly research shows cuteness builds unearned trust.
00:14:17: So some well-meaning employee just blindly clicks allow and suddenly hands over access to their entire corporate calendar, their email inbox.
00:14:26: And potentially they're payment credentials to a smiling cartoon...
00:14:29: ...and that leads to a severe systemic risk which need a kagopto brotha.
00:14:33: An agent doesn't actually need malicious sci-fi intent to be dangerous.
00:14:40: The danger lies in the combination of seemingly harmless permissions.
00:14:44: Imagine an agent tasked with just summarizing daily operational logs.
00:14:51: To do its job, it has permission to read your internal chat history.
00:14:54: that seems fine sure and It also his permission to create tickets in an external vendor system.
00:14:59: That also seems fine.
00:15:00: But when you combine them You just accidentally built a bridge for sensitive data to walk right out the front door.
00:15:06: Precisely
00:15:07: if that agent gets confused it might read a highly confidential internal Slack message about say an unannounced merger, and
00:15:15: just
00:15:16: helpfully exported into a public Zendesk ticket.
00:15:18: Yikes!
00:15:19: It's an unplanned data leak path created purely by combined
00:15:23: permissions.".
00:15:24: This is why Yahya Elmasius noted that cybersecurity companies are scrambling to build specific defenses for this.
00:15:30: Sentinel-I, for instance, just launched their Singularity Agentic Detection & Response System.
00:15:35: Oh interesting... Yeah it was built specifically to monitor the behavioral drift of these agents.
00:15:40: So if an agent suddenly stops summarizing logs and starts trying to export chat histories, the system stops at mid-action without crashing entire enterprise network.
00:15:49: That's
00:15:49: incredibly necessary!
00:15:50: But let me ask you a pointed question regarding high stakes fields — how does this wild west of permissions work in highly regulated spaces like healthcare or finance where drifting behavior doesn't just mean a leaked email?
00:16:03: It is creating massive friction because governance simply hasn't caught up with adoption speed at all In healthcare, Segeru Barrow made this really sobering comparison.
00:16:13: If you look at human medical residents they are required to undergo years of intensely supervised practice constant peer review attending physician sign-offs all before They Are ever allowed To make an unsupervised clinical decision
00:16:27: because a mistake literally means life or death.
00:16:30: right?
00:16:31: yet We're currently seeing clinical AI agents being deployed to monitor patient vitals flag early signs of sepsis and cross-check complex medication interactions entirely unsupervised.
00:16:43: That is genuinely terrifying!
00:16:45: We are essentially skipping the supervised residency phase for machines, a phase we legally mandate for humans.
00:16:52: Wow... And what about the financial sector?
00:16:55: Because if an AI agent hallucinates then initiates massive wire transfer.
00:16:59: you can't just politely ask for money back.
00:17:01: No You cannot And finance is realizing this and moving very aggressively to build walls.
00:17:07: Pradeep Sanyal highlighted a massive global shift, pointing new principles being issued in China.
00:17:13: What we're seeing?
00:17:13: that banks are positioning themselves as the ultimate authorization layer.
00:17:17: Okay explain how it functions mechanically Like if I explicitly tell my financial agent to execute a trade How does the bank stop?
00:17:24: It means user level permission no longer the final word.
00:17:28: Oh really
00:17:29: Yeah.
00:17:30: even if you explicitly authenticate and give your AI agent permission to move your money.
00:17:35: The bank's architecture can detect that the request is coming from an automated agent rather than a human interface, And the bank could simply refuse to recognize the agents authority.
00:17:45: The Bank decides What Your Agent Is Allowed To Do Inside Its Proprietary Systems Regardless Of What You Told The Agent To Do?
00:17:58: So the bank is playing bouncer at the door, rejecting the agent's ID.
00:18:02: Which brings up a strategic question for me.
00:18:05: if The risk of agents hallucinating or leaking data as this high Why don't companies just transfer their risks?
00:18:11: Like why not just buy insurance policies For their AI fleets?
00:18:14: Well Jamal Kay provided A brilliant reality check on the insurance market.
00:18:18: it turns out AI Agents are incredibly hard to insure right now
00:18:23: But Insurance Companies thrive On Risk.
00:18:26: I mean They insure coastal houses against hurricanes all the time.
00:18:29: They do.
00:18:30: but traditional insurance relies heavily on the mathematical principle of randomness.
00:18:35: Randomness,
00:18:36: okay And insurer doesn't know which specific house will be hit by lighting right?
00:18:41: But they know statistically how many we'll be hit across a vast Disconnected area.
00:18:46: so they can price that random risk
00:18:49: Right.
00:18:50: ai presents the exact opposite problem.
00:18:53: Thousands of different enterprises are building their custom agents on top the exact same handful underlying foundation models.
00:19:00: The risk isn't random, it is deeply correlated.
00:19:04: I see... So if a core foundation model suddenly degrades in quality or gets hit with like data poisoning attack It doesn't just cause one random claim and isolated company No!
00:19:15: It causes ten thousand catastrophic claims across multiple industries Triggering simultaneously in the exact same hour.
00:19:24: Oh wow, it's not a random house catching fire It's the entire neighborhood bursting into flames at the exact Same second because they all share the same faulty gas line.
00:19:32: That is a crazy visual right?
00:19:34: The insurance market just doesn't have the actuarial models to price that kind of correlated systemic risk.
00:19:39: yet.
00:19:41: So what does this all mean for the tech leaders listening?
00:19:43: We have massive architectural challenges.
00:19:45: we Have the psychological hurdles regarding accountability shadow AI running rampant and banks blocking agents at The door to me, This just proves we are not heading toward a single monolithic AI super
00:19:57: app.
00:19:57: No definitely not.
00:19:58: we are living in a deeply fragmented multi-vendor reality
00:20:02: absolutely because no single tech giant is going only entire agent ecosystem.
00:20:07: For the enterprise it's too vast.
00:20:09: yeah Alistair Greenwood summed this up perfectly.
00:20:12: He pointed out that asking what is the best AI agent platform, it's fundamentally a terrible question.
00:20:18: It really is!
00:20:19: There IS no single-best platform in a vacuum—it depends entirely on the gravity of your existing data workflows.
00:20:25: Like if you're entire company lives deep inside Microsoft's three sixty five ecosystem.
00:20:29: then architecting around co-pilot studio makes logical sense But If Your Sales and Marketing World revolves around massive sets CRM data You are naturally going to lean toward HubSpot AI.
00:20:39: And if we connect this fragmented reality to the bigger picture, it creates a new technical mandate.
00:20:45: Which is?
00:20:46: Because we have all these different platforms built by competing vendors living in different silos.
00:20:51: they urgently need a standardized way to talk to each other.
00:20:55: Amadoula Quadri Sayed explained a major development tackling this known as The A-to-A or Agent To Agent Protocol.
00:21:03: Agent To agent how does that actually work under the hood?
00:21:06: so right now If you want Two pieces of software to talk.
00:21:10: An engineer has to manually build a custom API integration between them.
00:21:14: Right, very tedious
00:21:15: Very The A-to-A protocol replaces that manual work by standardizing how independent agents discover each other autonomously.
00:21:24: It utilizes something conceptually called an agent
00:21:26: card An Agent Card.
00:21:28: Yeah you can think if it's like a digital business card That an agent broadcasts It details its specific identity its security clearances and it's capabilities.
00:21:38: Oh, that's clever!
00:21:39: This allows a Microsoft-based agent to seamlessly discover a Salesforce based agent verify its credentials negotiate a delegated task in stream status updates back and forth entirely independent of the frameworks they were originally coded into.
00:21:53: That interoperability is crucial.
00:21:56: otherwise you just have a bunch of highly intelligent isolated digital workers who refuse speak the same language.
00:22:01: It Is The Only Way To Scale And Pamela Fox shared some dispatches from recent developer conferences, specifically AGNTCon and MCPCon showing just how fast this interoperable ecosystem is advancing.
00:22:14: Like they are already developing OAuth for these protocols.
00:22:19: Now OAuth is what allows me to like use my Google account To log into a random third-party website securely right?
00:22:24: Exactly
00:22:25: Why
00:22:25: is OAuth an agent such big deal?
00:22:28: Because right now, agents often have to piggyback on human credentials.
00:22:31: They essentially pretend to be you.
00:22:33: Oh okay
00:22:34: Oauth for Agents means they will soon be able to securely authenticate themselves interact with external servers and leave an audit trail using their own unique independent identities.
00:22:45: The system will know exactly which agent took which action without tying it back to a human user's login.
00:22:51: Okay, let me throw a final strategic question at you then.
00:22:54: Sure With all these distinct agents from competing vendors securely authenticating and delegating tasks to each other across different networks Are we just building a highly efficient digital tower of Babel or is there a unified end goal?
00:23:08: To all of this interoperability?
00:23:09: Well that is the ultimate question for the next decade of enterprise tech Visio Ipondi drawing on insights from Cisco in Google DeepMind He framed the trajectory beautifully.
00:23:20: What did he say?
00:23:21: He pointed out that the industry has spent the last few years fiercely focused on making individual models smarter.
00:23:27: That was phase one,
00:23:28: right The brute force race to build the smartest single
00:23:32: chatbot exactly.
00:23:34: but that phase is ending.
00:23:36: The next massive frontier for the enterprise is scaling collective intelligence.
00:23:40: collective intelligence.
00:23:42: The goal isn't one omniscient AI.
00:23:45: The goal is figuring out how to get a massive swarm of specialized multi-vendor agents, To establish a shared intent.
00:23:53: Coordinate complex decisions autonomously and become collectively smarter And more capable than any single model could ever be on its own
00:24:02: Going from isolated intelligence to a coordinated collective Intelligence operating at an enterprise scale that completely rewrites the boundaries Of what a business Is actually capable of executing.
00:24:14: It is a fundamental paradigm shift in organizational design.
00:24:27: And
00:24:36: if you review your own enterprise architectures and roadmaps this week, I want to leave you with one final thought to mull over based on some fascinating research from Peter Slattery regarding a genetic inequality.
00:24:48: A genetic inequality?
00:24:49: Yeah
00:24:50: as these autonomous delegates become vastly more capable of complex planning and real world action they are inevitably going to shape the distribution of
00:24:59: power right
00:25:00: we have.
00:25:02: Will the deployment of these AI agents simply deepen existing corporate and societal divides, creating a reality where entities with the highest quality in quantity of agents pull impossibly far ahead of everyone else?
00:25:15: Or can we proactively design governance models today that actually mitigate those devices.
00:25:21: If we don't build the steering wheel on the brakes right now it's simply won't matter how powerful the engine is when finally hit the curve.
00:25:27: A perfect thought to close.
00:25:29: Keep building those brakes, everyone.
00:25:30: We will see you on the next Deep Dive!
New comment