Begin with the outcome, not the logo
Describe the result. Auto considers the task, your routing preferences, and which connections are actually available. You can override it whenever a particular model must do the work. Availability is a configuration fact, not a promise that the cheapest or best model on the market is in the room.
Keep simple work simple
A single-model route answers a question without automatically buying four opinions. Use a team workflow when another perspective is worth the extra calls. Multiple responses can surface disagreement. They also consume extra usage. Make that a decision, not a default.
Make research a distinct step
An explicit research request uses the connected research capability and keeps source links. It is separate from a build. Asking for facts does not silently authorize a code change. That boundary is the difference between a chat and a workplace.
Judge the route by the useful result
A cheap answer that needs three retries can cost more than one capable call. Independent review can be cheaper than a production incident. Symphony’s routing does not guarantee the market’s lowest price or equal quality across providers. It gives you a repeatable way to compare.
Inspect, then decide the next call
Read the answer, the sources, the proposed change, and the activity. When a request fails, the failure stays visible. Narrow the task or choose a different available connection. Do not treat model agreement as proof.