Real engineering happens in legacy codebases, not blank canvases. This session explores deploying multi-agent AI workflows using Kiro against brownfield production systems with tangled dependencies and accumulated technical debt. Learn how to orchestrate specialised agents for system mapping, dependency navigation, code generation, and validation within complex existing architectures. We'll examine practical strategies for providing sufficient context to agents, implementing guardrails to prevent regressions, and coordinating multiple agents toward shared goals. Walk away with actionable techniques for applying agentic AI to real-world codebases, understanding where automation delivers value and where human judgment remains irreplaceable.
What this session is about
Playbook
Editorial commentary · what to actually do about this on Monday
The concept
Multi-agent workflows on legacy codebases. Specialised agents for system mapping, dependency navigation, code generation, and validation.
Why it matters
Brownfield is where real engineering happens. AI tools that only work on greenfield are useless for most enterprises.
The hard parts
Providing sufficient context to agents in tangled codebases. Coordinating multiple agents toward shared goals without thrashing.
Playbook moves
(1) Start with read-only mapping agents. (2) Add modification agents only after the map is verified. (3) Limit specialist count — coordination overhead beats specialisation gains beyond a small number.
The surprise
The right number of agents is rarely the obvious one. Two specialists usually outperform five. Multi-agent designs that look organised in diagrams often thrash in production. Default to fewer until you can name the specific reason you need more.
---
Independent editorial perspective — not an official AWS or speaker statement. Designed for executives evaluating what to brief their teams on next.
Live updates related to this session LIVE
Sourced via Parallel AI Monitor — continuous web watch on 21 topical streams. Updated .
- labs.cloudsecurityalliance.org high confidence Agent identity & delegation
NIST AI Agent Standards: Enterprise Governance Implications
Fastio has formalized new architectural patterns for scaling multi-agent systems, including Sequential Handoff (Pipeline), The Router (Dispatcher), Hierarchical (Manager-Worker), and Bidirectional/Joint Collaboration. A significant practical implication is the emergence of 'Deleg
- developers.googleblog.com high confidence Multi-agent collaboration patterns
Announcing the Agent2Agent Protocol (A2A) - Google Developers ...
Google introduced the A2A (Agent2Agent) protocol, a standardized communication framework designed to enable interoperability between AI agents across different frameworks, teams, and organizations. Launched as part of a broader agentic suite at Google Cloud Next 2026, it includes
- linkedin.com high confidence Multi-agent collaboration patterns
A2A Net
Google introduced the A2A (Agent2Agent) protocol, a standardized communication framework designed to enable interoperability between AI agents across different frameworks, teams, and organizations. Launched as part of a broader agentic suite at Google Cloud Next 2026, it includes
- edu.google.com high confidence Multi-agent collaboration patterns
Learning Tools & Educational Solutions
Google introduced the A2A (Agent2Agent) protocol, a standardized communication framework designed to enable interoperability between AI agents across different frameworks, teams, and organizations. Launched as part of a broader agentic suite at Google Cloud Next 2026, it includes
- union.ai high confidence Decision lineage & audit trails for agents
Agentic AI - Union.ai
New analysis of Gartner's 2026 predictions indicates that the Context Graph is the critical architectural gap that agents must fill to ensure reliable and scalable decision-making within enterprise settings.
External links matched to this session via topic relevance. The KB does not endorse third-party content; verify before citing.