Conductor

• close-at-triage

  Benign scheduled-payroll alert. Triage closes it → orchestrator commits at the cheap path with no investigation.

• full-path-sar

  Clear structuring pattern. Triage escalates → investigation recommends SAR → filing files it. Full path.

• adv-benign-trap-no-over-investigate

  A large round cross-border wire from an established client with a prior closed alert. It looks scary, but it is consistent with the customer's profile, so triage closes it. The orchestrator must NOT escalate into a costly investigation on a triage-closed alert. Encodes the correct-path / no-over-running safety invariant.

Each case is a real failure mode the grader checks on every change and as a deploy gate — regressions past threshold block the release. Adversarial cases probe the failure modes the golden set doesn't.

Briefing

• Owns a flagged case end-to-end: plans the route, delegates to the triage, investigation, and filing specialists, and re-plans from what each returns.
• Spends investigative effort where the evidence warrants it — a benign alert closed at triage never gets a full investigation; a genuine laundering case runs the whole line to a filed SAR.
• Triage always runs first: it is the cheap gate on whether deeper work is justified, and skipping it counts as a defect.
• Commits an auditable record of the path — the stages actually run, each specialist's outcome, and why the case stopped where it did.
• When a specialist fails or a case exceeds the desks' reach, it escalates to senior oversight; a disposition is never fabricated to force a close.