Edouard Maleix - How AI-First Dev Teams Build Collective Intelligence — One Attributed Mistake at
The talk outlines a comprehensive workflow for transforming isolated agent mistakes and learnings into reusable, attributable collective intelligence within development teams. Instead of relying on simple documentation or context window stuffing, the proposed system introduces several primitives—Identity, Diary, and Knowledge Packs—to ensure that every incident, fix, and decision is captured, linked, validated, and made available to future work, thereby accelerating team learning beyond human pace.
Key takeaways
-
The Problem with Isolated Learning
1:42
Agents' small discoveries and incidents often remain trapped within a single session (e.g., closed PRs or chat history), leading to the evaporation of corrections and preventing knowledge from becoming reusable.
-
The Need for Structured Knowledge Capture
3:58
Teams need more than just a wiki; they require a 'knowledge factory' that catches mistakes, interruptions, and turns them into validated guidance. This knowledge must be constantly evolving (live, die) rather than static.
-
The Importance of Agent Identity
14:15
Giving agents a unique identity with signed commits and access rules solves the problem of attribution masking. It establishes a clear actor boundary, preventing agents from operating under human permissions.
-
The Diary Primitive
15:30
The 'Diary' serves as the central home for all discoveries and decision-making ('what the F moment'). It allows work/decisions to be linked to specific entries, providing reasoning beyond just diffs and commit messages.
-
Creating Reusable Knowledge Packs
21:45
The process involves capturing an incident (Entry) $ ightarrow$ grouping related Entries into a 'Pack' $ ightarrow$ rendering the Pack into usable markdown/context for the agent. This ensures lessons are traceable back to the original failure.
-
Validation and Evaluation (Evals)
27:20
To ensure quality, two types of evaluation are necessary: checking if the Pack is 'true to the entries' (fidelity) and running a task that reproduces the original incident using the knowledge pack to measure improvement (usefulness).