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 .
- aiworkflowlab.dev high confidence Multi-agent collaboration patterns
Multi-Agent AI Systems: 2026 Guide | AI Workflow Lab
Swarm vs Hierarchical Orchestration Analysis: A study of production data in 2026 indicating that hierarchical orchestration typically outperforms 'swarm' patterns (peer agents coordinating without a central orchestrator) on most real-world workloads. Use case: Determining the opt
- azion.com Scaling infra for agent workloads
Understanding Agentic AI Infrastructure
Gravitee published an update explaining that the stateless Model Context Protocol (MCP) specification simplifies horizontal scaling for agent workloads. The update also highlights AI gateway governance as a way to manage agent tool traffic, security, and scaling across MCP-based
- callsphere.ai high confidence Multi-agent collaboration patterns
Swarm Patterns: When Hierarchical Agents Beat Flat ...
Swarm vs Hierarchical Orchestration Analysis: A study of production data in 2026 indicating that hierarchical orchestration typically outperforms 'swarm' patterns (peer agents coordinating without a central orchestrator) on most real-world workloads. Use case: Determining the opt
- nist.gov high confidence AI agent regulation & policy
AI Agent Standards Initiative | NIST
OWASP released the 'Top 10 for Agentic Applications 2026', establishing the first dedicated security framework for autonomous AI agents to address vulnerabilities and risks associated with agentic AI systems.
- digitalapplied.com high confidence Multi-agent collaboration patterns
Agent Architecture Patterns: 2026 Taxonomy Guide
Swarm vs Hierarchical Orchestration Analysis: A study of production data in 2026 indicating that hierarchical orchestration typically outperforms 'swarm' patterns (peer agents coordinating without a central orchestrator) on most real-world workloads. Use case: Determining the opt
External links matched to this session via topic relevance. The KB does not endorse third-party content; verify before citing.