Speaker notes: Welcome. Teasing: “Session 5: we gave the model hands. Session 6: we put it in a loop. Today, two leaps: we go from the employee to the company, and we invent the USB port for AI.” Announce the two halves of the session: multi-agent (1st hour), MCP (2nd hour).
Speaker notes: 2 minutes max. Have a participant recite the loop. The golden rule from line 4 will return in a multi-agent version: “if one agent is enough, no team”.
Speaker notes: Clear contract. Reassure: “No code to write today — but at the end, you will be able to draw the complete architecture of a professional multi-agent system, MCP included.”
Speaker notes: Common theme of the session: NewsRoom 📰. Let the room listen for 2 minutes before showing the next slide. Write their answers on the board — most of the 4 problems will emerge on their own.
Speaker Notes: Relate each point to past sessions: point 2 = violation of least privilege (S5); point 4 = working memory (S6) which overflows. Punchline: “It works…until the day it doesn’t work anymore, and when that day comes, you won’t know why.”
Speaker notes: THE conceptual slide of the 1st hour. The business analogy will carry the entire session: “you don't hire ONE person to do everything — not because it's impossible, because it's fragile.” The accountant has the key to the safe, not the intern.
Speaker notes: Trap No. 1 of the session to be defused immediately: the 4 agents can work on the same Claude/GPT. What's different: prompt, tools, safeguards. Agency was a property of the system (S6); specialization too. Note that the Editor has NO tools: an agent can be “naked”.
Speaker Notes: “The assembly line.” Use cases: document processing, content generation, intelligent ETL (Extract-Transform-Load). Ask the question of rejection: we need to go back to the Editor — and already the pure pipeline is cracking. Transition: “what if the steps were not known in advance?”
Speaker notes: “The project manager.” THE distinction with the pipeline (quiz question!): pipeline = path set by the developer; orchestrator = path decided by the model at runtime. Use case: “complete file on company X” — the breakdown depends on the case. Insist: everything goes through the boss, so if he breaks it down badly, everything fails.
Speaker notes: Use case for this audience: validation of a regulatory analysis before sending to the regulator. Convergences give confidence, divergences trigger human review — it is an uncertainty detector. To be reserved for decisions that merit the additional cost: “not for the morning summary, yes for the advice to the regulator”.
Speaker notes: The orchestrator/supervisor confusion is THE pitfall of the quiz. Formula to repeat: “the project manager vs quality control + compliance manager”. The two are often combined — especially in finance, health, legal. The supervisor detects: infinite loops, off-topic, rule violations.
Speaker notes: Slide to photograph. The column “who decides the flow?” is the reading key. Specify that the bosses COMBINE: pipeline + supervisor, orchestrator + debate on a critical step, etc. These are bricks, not exclusive squares.
Speaker notes: Exact symmetry of the rule of Session 6 (“if a prompt is enough, no agent”). A credible trainer says when NOT to use their tech. Example: “rephrase this email” → a prompt. Point. Transition: “Let’s move on to manipulation.”
Speaker notes: Sequence C of the guide. Circulate around the room. Debrief question: “Who decides the path in each pattern?” The correct verbalization: pipeline = fixed in advance, orchestrator = decided by an agent. If not enough laptops: you control the video projector, the guide room.
Speaker notes: Launch the teaser before the break: “Question to ponder over coffee: your 4 agents must share their results. Like in a business, there is email, the network folder, and the meeting whiteboard. Guess: it's the same for agents.”
Speaker Notes: The business analogy does all the work.The blackboard: STRUCTURED common space (sections, statuses) where an agent “wakes up” when information that concerns them appears — NewsRoom: the Checker is triggered as soon as a draft is posted. Messages = natural mechanism of the pipeline and orchestrator.
Speaker notes: Pivotal of the session — take care of the transition. “First hour: the agents among themselves. But the Researcher has to talk to web search, the Publisher to Slack… Each connection was custom code. Let's see the extent of the problem.”
Speaker Notes: Draw the 12 arrows on the board if possible — the visual effect of the spaghetti dish is worth a thousand words. Each arrow = code, authentication, maintenance, bugs, redone each time. Question to the room: “Does this remind you of a problem that has already been solved in IT?” → next slide.
Speaker Notes: The official analogy — and it is apt. Explain the acronym (course rule): Model Context Protocol. Emphasize “open standard”: initiated by Anthropic but not owned by anyone in practice — this is the condition for a standard to work. ⚠: dates and adoption change quickly, check before each session.
Speaker notes: THE slide to know by heart — this is question 8 of the quiz. Expand: the host hosts the model and decides which servers to connect; the client manages ONE connection (3 servers = 3 clients in the host); the server exposes the capabilities. Open tab 2 of the parallel page: the diagram is clickable there.
Speaker notes: Defuse head-on: half the room imagines the cloud as soon as they hear “server”. Useful reformulation: “an MCP server is an ADAPTER placed in front of an existing service, which translates it into standard MCP language”.
Speaker notes: THE column that counts: “who decides”. Tool → the model acts (with guardrails S5–S6). Resource → the app chooses what to show (RAG spirit, S4). Prompt → the user draws from a menu. Trick question to ask: “a tool `lire_fichier` and a resource file, what’s the difference?” → the trigger. Same data, different control — and in production, control is the whole point.
Speaker notes: The slide that ties it all together. Insist on continuity: MCP does not replace tool calling, it STANDARDIZES it (analogy: USB has not replaced keyboards, it has standardized the socket).Participants should walk away feeling like they already knew 80% of MCP without knowing it.
Speaker notes: Message of pure economy: weeks of development avoided. ⚠ on the entire list: the ecosystem moves quickly, possibly show an up-to-date directory if you have a network (otherwise, the page contains a static catalog). Transition: “and when your business logic doesn’t exist on the shelf?”
Speaker Notes: Three messages: (1) each `tool` = exactly the S5 tool definition — name, description, diagram: “you already know how to do it”; (2) written ONCE → all your hosts benefit (the N+M gain); (3) security does not change — least privilege, human validation for the irreversible. No one should copy the code: it is conceptual pseudo-code.
Speaker Notes: The final photo that brings the ENTIRE session (and sessions 5–6) together. Have a participant comment on it: boss? communication ? MCP primitives used? guardrails? If he can explain everything, the session is won. “You now have all the pieces of a professional multi-agent system.”
Speaker notes: Quick reading, then express oral quiz (5 questions from the quiz file) and distribution of exit tickets. Point 6 last, voluntarily: it is the discernment which distinguishes a professional from a follower of fashion.
Speaker Notes: The weekly challenge creates continuity and provides real cases for the next opening session. Say thanks, stay 5 minutes for individual questions — that's often where the real business use cases come out.