Model routing

Route a portfolio. OpenAI supplies the capability baseline, GLM supplies broad family diversity, and Grok supplies implementation, debugging, and adversarial diversity. The parent chooses a model for each launch. Keep ticket role configurations model-neutral.

1. Classify the roles

Assign each role exactly one route class:

• Throughput: breadth matters, attempts are independent, and a weak result is cheap to discard.
• Routine: correctness, coherence, or sustained reasoning matters, including difficult first attempts.
• Reviewer: independently assess work against one review axis.
• Synthesis: consolidate completed review reports without performing another review.

Mark these diversity triggers where they apply:

• Frontend: visual direction, interaction design, composition, or polish.
• Alternative candidate: a competing approach, implementation, interface proposal, design, or prototype.
• Grok diversification: a diagnosis remains uncertain or a fix failed, a competing implementation could expose a material tradeoff, or correlated OpenAI and GLM assumptions would be costly.
• Adversarial review: failure-oriented review, debugging, race or concurrency analysis, assumption challenge, or a merge gate.