Model portfolios need routing rules

A note on keeping model portfolios small, named, and evaluated.

A model portfolio only helps when each route has a reason: reasoning depth, code execution, privacy, cost, latency, or fallback resilience. Without named routes and review checks, a portfolio becomes preference drift rather than workflow design.