A single planner query at Meridian sometimes needs both a charter-clause lookup and a customs-tariff lookup answered together in one response, and each lookup requires a different specialized retrieval corpus and different domain logic. Which Agent Bricks pattern is purpose-built for orchestrating this kind of multi-domain request?
Select an answer to reveal the explanation.
Short Explanation
One question, two totally different specialties needed at once - that's a job for a supervisor who knows which specialist to hand each half of the question to and then stitches the answers back together, not one generalist trying to wing both.
Full Explanation
Multi-Agent Supervisor is the right pattern because the requirement explicitly involves two distinct domains with different retrieval corpora and different domain logic that need to be combined into one response - which is the exact orchestration problem a supervisor agent solves by routing each sub-task to the specialized agent equipped for it. Knowledge Assistant over a single merged corpus is the wrong move because charter clauses and customs tariffs are governed by different logic and structure; merging them into one corpus degrades retrieval precision for both rather than preserving each domain's specialization. Information Extraction is the wrong pattern because the planner is asking an open-ended combined question, not requesting a fixed set of structured fields pulled from documents. Concatenating both corpora into one giant context window does not solve the orchestration problem either - it burns context budget, loses the benefit of domain-specific tool logic, and risks the model conflating clause language with tariff language. The exam-relevant distinction is single-domain-with-citations (Knowledge Assistant) versus multi-domain-requiring-routing (Multi-Agent Supervisor).