Case Study: Scout as Orchestrator Workers

Suppose a store manager signs a contract with a shipping carrier because a research report rated its damage rate the lowest of four. A week later she finds that no page the agent read contains that damage rate. The report looked complete, and nothing in it set the unsupported figure apart from the sourced ones.

This case study designs Scout so that such a report cannot be saved. The design keeps three rules. Every claim points to a saved source, and code confirms that the quoted text exists in that source. A failed search appears in the report as a named gap rather than as silence