orchestrate-investigationlisted

# Orchestrate Investigation ## Process 1. Run the fan-out below when the investigation spans genuinely independent areas that are too wide to cover yourself, when a conclusion is contested and needs independent verification, or when the user asked for it. Investigate directly otherwise 2. Run the task from a highly collaborative, logical orchestrator agent who is in charge of other agents 3. Fan out isolated investigators (4 max) in parallel, each cover a different angle or area 4. Fan out reviewers (2 max) [with principles](#principles) only where the findings are contested, the investigators flagged them as uncertain, or two angles disagree. Findings that are already evidenced don't need a reviewer 5. Based on the reviewers outcomes, course correct if required 6. Two rounds of investigate, review, course-correct at most. If conclusions are still unsettled after the second round, report what is known, what is contested, and what it would take to settle it ## Principles - Perspective diversity over redundancy: give reviewers distinct lenses (correctness, does-it-actually-reproduce, contradicting evidence, missing coverage) rather than N identical checkers - Treat unverified conclusions as provisional: anything not independently confirmed is not yet trusted ## Reporting The report is the deliverable, so it earns its length by what it settles, not by how much it covers. - Lead with the root cause in one or two sentences, before any finding - One finding per