Robots Talking
Cracking the Code of Artificial Intelligence: A New 2D Blueprint for Building AI Agents with LLMs Have you ever wondered how the complex artificial intelligence systems we interact with are actually organized behind the scenes? As the world rapidly adopts AI agents powered by LLMs (Large Language Models), tech companies have been scrambling to write the instruction manual for how to build them. But until recently, everyone was looking at the problem from a fundamentally different angle. A fascinating piece of research by Jia Huang and Joey Tianyi Zhou introduces a groundbreaking way to understand and build these digital assistants. They discovered that the current way we think about AI design is incomplete—and they've proposed a "Matrix" that changes how we view the architecture of AI. The Problem: Looking at Just Half the Picture Before this research, tech giants were essentially speaking different languages when discussing agent design. Frameworks from companies like Anthropic and Google focused mostly on the "wiring" or execution topology—meaning, how data flows from one step to the next. Meanwhile, cognitive science surveys focused purely on the brainpower or cognitive function—meaning, what the agent actually does. To put it in human terms, relying on just one of these viewpoints is like looking at a corporate organizational chart that shows a "Manager" assigning tasks to "Workers". You know the structure, but you still have no idea what the company actually does. That exact same manager-to-worker setup could be used to break down a complex project, consult specialized experts, or simply monitor a system for errors. Because these tasks have completely different risks, costs, and testing needs, looking at just the structure or just the task makes it impossible to fully understand the system. The Solution: A Two-Dimensional Map for AI To solve this, the researchers created a framework that combines both the "What" and the "How" into a single, two-dimensional coordinate system. * The "What" (Cognitive Function): This axis looks at the seven core steps an AI takes to process information: Context Engineering (what information it pays attention to), Memory, Reasoning, Action, Reflection, Collaboration, and Governance (the rules and boundaries it operates within). * The "How" (Execution Topology): This axis identifies six ways to wire the system together: linear Chains, conditional Routes, Parallel multitasking, centralized Orchestration, repeating Loops, and nested Hierarchies. By crossing these two dimensions, the researchers discovered a 7x6 matrix containing 27 distinct blueprints (or design patterns) for building AI agents. Real-World Findings: The 5 Laws of AI Design To prove this wasn't just theoretical, the team tested their matrix across four real-world industries: financial lending, legal due diligence, telecom network operations, and emergency room healthcare triage. From analyzing these wildly different use cases, they discovered five universal "laws" that govern how artificial intelligence must be structured: 1. Time limits dictate complexity: If an AI has 8 hours to review a stack of legal contracts, it can use a complex, hierarchical team structure. But if an ER triage AI only has 60 seconds to assess a sick patient, it must use the simplest, fastest straight-line "Chain" structure. 2. Higher stakes demand tighter rules: If an AI agent is allowed to take action on its own (like fixing a broken computer network), it needs strict "Blast Radius" controls to limit potential damage. If it only gives advice, an "Approval Gate" where a human has the final say is perfectly sufficient. 3. The cost of failure changes how AI reflects: When reviewing bank loans, false positives and false negatives are equally bad, so the AI simply checks its work for pure accuracy. But in healthcare, mistakenly sending a critical patient to the waiting room is catastrophic. In these high-stakes cases, the AI's self-critique phase must be deliberately biased toward playing it safe. 4. Work volume demands teamwork: A single task doesn't require collaboration. But reviewing 500 legal contracts requires the AI to adopt a "Fan-Out/Gather" pattern, splitting up the work to process it simultaneously before synthesizing the final results. 5. Context is everything: A single blueprint acts completely differently depending on the job. An AI double-checking its own work might take 5 minutes to verify a bank loan, but only 30 seconds to verify an IT alert. The blueprint provides the how, but the industry provides the what and why. Why This Matters for the Future As LLMs become more advanced, the way we string them together matters just as much as the models themselves. This new framework acts as a universal, durable vocabulary for software engineers. Whether a model can remember 4,000 words or 2 million words, the fundamental need to structure what the AI thinks and how it processes that thought will remain exactly the same.
70 episodios
Comentarios
0Sé la primera persona en comentar
¡Regístrate ahora y forma parte de la comunidad de Robots Talking!