Model Orchestration

Apply intelligence where it most improves a verified, usable outcome. Optimize whole-task cost and delay, including context duplication, coordination, verification, and likely rework, while preserving required quality and authority. These are allocation principles, not a mandatory multi-agent workflow. Explicit project requirements remain binding.

1. Keep ownership with useful context

The agent holding the user's intent and relevant project context owns the integrated result. It may plan, draft, implement, run checks, and refine directly. Roles describe responsibilities; they do not require separate workers.

Keep tightly coupled work together when a handoff would mostly make another agent reconstruct the same understanding. Completing the task in one capable context is a valid orchestration choice, not a failure to delegate.