- Published on
The orchestrator diagram is clean, and every arrow on it is a billed network call to a model. A panel multiplies cost and floors latency at its slowest member; a pipeline adds latency and compounds error. Budgeting fan-out per specialist across three levers - model tier, call frequency, and cacheability - and the cases where the cheapest correct answer is not to fan out at all.