stationslisted

# stations A kitchen runs fast because each station cooks its own dish: garde manger does not wait for the grill. But the speed comes from the cuts being made before service, and two cooks at one board ruin both dishes. This skill is the expeditor's fan-out: deciding what is genuinely separate work, giving each station a complete ticket, and tasting everything together before it leaves. **Core principle:** parallelism is earned by proving independence, not assumed from the symptom list. The fan-out is the last step of triage, never the first move. ## Triage before any dispatch The expensive mistake is dispatching one agent per symptom. Symptoms group by root cause, and a refactor that broke four things usually broke two things twice. 1. **Cluster by suspected cause, not by file.** Two failures in different test files that both touch the same layer (the same data shape, the same recent change) are one cluster until proven otherwise. Check what actually changed (`git log`, the refactor's diff) before declaring anything independent. Symptoms living in different files is not independence; it is the same bug crashing in two places. 2. **One cluster, one station.** A shared root cause dispatched to two agents buys two local symptom patches that each make their own test green and disagree with each other - one patches the data producer, the other patches a consumer, and the suite is green while the design is incoherent. The cluster goes to a single agent with the whole picture,