Collaboration, Control & Parallel Agents

Share intermediate results through a blackboard.

Lessons

7 lessons

Deliverable: Parallel retrieval: run the sub-questions of a decomposed query as parallel agents and stream partial answers, then report the latency saved.
Assessment: Answer the five Interview questions without notes, then run the lab.
Interview probe: Larkspur's support assistant now answers each part of a compound question in a parallel branch. Since the change, some replies to "refund, export and outage credits" questions say nothing about credits, and the trace shows two synthesizer outputs for one request. What happened, and how do you fix it?
Common mistakes: Relying on recursion_limit instead of a specialist-call cap to stop the controller
Having agents debate which of two retrieved refund policies is current
Joining parallel branches with separate edges instead of a list edge

How confident are you with this module?

1 means "I could not explain it yet"; 5 means "I could teach it". Rate again any time.

Your notes on this module

Saved in this browser when you leave the box.