You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[P1] Replace fixed model routing with dynamic selection and pinned choices #32
The current policy publishes exact Gemini model IDs and role defaults. Model catalogs change across vendors, plans, and hosts. Those IDs should not define the public workflow contract.
Deliverable
Replace fixed public model routes with runtime selection through the adapter contract from #31.
Define stable internal preferences:
fast: minimize latency and cost for bounded work
balanced: default quality, speed, and cost
deep: spend more budget on difficult reasoning, planning, or review
Keep reasoning effort separate from the preference. Treat vendor family names such as Flash, Pro, Opus, Sonnet, and Haiku as adapter hints only.
The orchestrator must record and pin the selected choice for retries and resume.
Acceptance criteria
No published skill contract requires a vendor or exact model ID.
Adapters expose live model availability, supported effort levels, and relevant capabilities.
The orchestrator selects from current candidates using task requirements, static security constraints, availability, quota, and the internal preference.
A family hint never grants permissions or acts as a cross-vendor quality guarantee.
routing-outcomes.json records vendor, adapter, exact model ID, family hint, preference, effort, catalog or probe revision, selection reason, and every attempt.
Normal retries use the recorded model and effort.
Quota exhaustion or operational failure does not silently switch providers or models.
A missing pinned model requires an explicit, recorded fallback or handoff.
Activity
anthonyandrei commentedon Sep 4, 2026
Resolved by PR #39 (#39). The merged implementation covers this issue, and the targeted acceptance tests pass. Closing as completed.