---
theme: seriph
title: "Lesson 42 — How Do Agent Teams Fail—and What Should We Build Next?"
info: "English video course for AI Agents in Depth"
author: Bojie Li
transition: slide-left
mdc: true
lineNumbers: false
monaco: false
aspectRatio: 16/9
canvasWidth: 980
layout: cover
class: cover
---
Expand · Chapter 10 · Multi-Agent Collaboration
# How Do Agent Teams Fail—and What Should We Build Next?
Conflicts, error cascades, Agent societies, and the course synthesis
Lesson 42 of 42 · 18 minutes · Failure Modes; Agent Society; Economic Competition; Strategic Gameplay
---
layout: center
class: text-center
---
The central question
How do we prevent local mistakes from becoming group failures while still allowing collective behavior to emerge?
---
# Why this problem matters
Concurrency
Shared files can lose updates or encode semantic conflicts.
Cascades
A wrong upstream claim is amplified by trusting downstream Agents.
Emergence
Persistent Agents produce social, strategic, and economic behavior not explicitly scripted.
---
# Three ideas to keep in view
Optimistic locking
Detect version change before committing a shared write
Information control
A code judge reveals only what each role may know
External reward
Society outcomes are scored by the environment—not self-report
---
# The book's visual model
Voice Werewolf multi-Agent system
---
# Agent chat room vs. Governed society
Agent chat room
- Everyone sees everything
- Loose role prompts
- Claims spread unchecked
Governed society
- State authority in code
- Role-scoped views
- Auditable actions and rewards
Social complexity requires stronger state and information governance.
---
# The judge owns truth and disclosure
~~~python
private_view = judge.view_for(player, global_state)
action = player.act(private_view)
judge.validate(action, role=player.role)
global_state = judge.apply(action)
audit.append(player.id, action, state_hash(global_state))
~~~
---
# Test the claim
10-8 offline diagnostic2 min
Run a deterministic information-isolation game
Observe: Private role context, phase transitions, legal actions, votes, and winner gates
Demo budget: 2 minutes · one contiguous terminal block
---
class: course-terminal
---
Live demo
# Switching to the terminal
~~~bash
$ cd chapter10/voice-werewolf && python demo.py --offline
~~~
Run the command(s), narrate decisions, and point to the observation—not just the output.
---
# What the evidence supports
Finding 1
Coordination failures are distributed-systems failures plus probabilistic decision errors.
Finding 2
A code-driven authority can preserve information asymmetry and rule integrity.
Finding 3
Social and economic simulations can generate new experience—but also collusion and pathology.
---
layout: center
---
Where the claim stops
# Boundary condition
An offline all-AI diagnostic does not satisfy the book's live human voice acceptance criteria.
---
layout: center
---
Engineering takeaway
# Design rule
Keep shared truth, permissions, conflict detection, and final rewards outside the Agents that compete or collaborate.
---
# Continue the experiment
---
# The complete course arc
Build · Lessons 01–21
Context → memory → tools → code
Improve · Lessons 22–34
Evaluation → training → continual evolution
Expand · Lessons 35–42
Voice → embodied action → collaboration
---
layout: center
class: text-center
---
Pause and apply
# Your turn
Which group-level failure cannot be prevented by improving any single Agent in isolation?
---
layout: center
class: text-center
---
Course synthesis
1Define the failure
→
2Run a controlled experiment
→
3Interpret the evidence
→
4Update safely
↺ Repeat when new evidence arrives
