Europe 2026
The Multi-Agent Architecture That Actually Ships — Luke Alvoeiro, Factory
Overview
This talk introduces Missions, a multi-agent system designed to tackle complex software development tasks that extend beyond a single agent's capacity. The core thesis is that human attention, not intelligence, is the current bottleneck in software engineering. Missions aims to overcome this by enabling systems to execute tasks autonomously for extended periods, allowing human engineers to focus on higher-level strategic decisions.
Who should watch
- AI Engineers
- Product Managers
- Builders working on agentic systems
- Those facing bottlenecks due to limited human bandwidth for task supervision
- Individuals interested in scaling agent capabilities for complex projects
Key takeaways
- The primary bottleneck in software engineering is human attention, not model intelligence, limiting the number of tasks that can be supervised.
- Multi-agent systems can be categorized into five patterns: delegation, creator-verifier, direct communication, negotiation, and broadcast.
- Missions integrates delegation, creator-verifier, broadcast, and negotiation into a single workflow with a three-role architecture: orchestrator (planning), workers (implementation), and validators (verification).
- A critical component of Missions is the validation contract, defined before coding begins, which specifies correctness independently of implementation to prevent drift.
- Validation in Missions includes both traditional checks (tests, linting) and behavioral validation through user-like interaction with the live application, which is time-consuming but crucial for end-to-end correctness.
- Structured handoffs detailing completed work, issues, and commands are used to maintain context and enable self-healing within the system.
- Missions prioritizes serial execution of features with targeted parallelization for read-only operations to dramatically reduce error rates and ensure correctness over long runs.
- The system's architecture is designed to improve with each model release, with orchestration logic primarily defined in prompts and skills rather than hard-coded states.
Notable quotes
*The bottleneck in software engineering nowadays is not intelligence. It's now limited by human attention.*
*Tests written after implementation don't catch bugs. They confirm decisions.*
*The ability to put the right model in the right seat becomes a compounding advantage.*
Unofficial community note. Prefer the recording for nuance.